Hola Thorsten!
yes as Jos already pointed out, the XPointer frameowrk classes are
generated by a JavaCC grammar :)
All the best, hasta pronto!
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
On Thu, J
On 01/19/2012 11:14 AM, Jos Snellings wrote:
Hi Thorsten,
They are under
generated-sources/javacc/org/apache/cocoon/sax/xpointer/ParseException.java
Apparently the java is only generated at build time. Don't know
details (pom.xml has javacc-maven-plugin).
Thanks, yeah that makes much sense
Hi Thorsten,
They are under
generated-sources/javacc/org/apache/cocoon/sax/xpointer/ParseException.java
Apparently the java is only generated at build time. Don't know details
(pom.xml has javacc-maven-plugin).
Jos
On 01/19/2012 10:56 AM, Thorsten Scherler wrote:
Hi all,
in
https://svn.ap
Hi all,
in
https://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-sax/src/main/java/org/apache/cocoon/sax/component/XIncludeTransformer.java
we do
import org.apache.cocoon.sax.xpointer.ParseException;
...
import org.apache.cocoon.sax.xpointer.XPointerFrameworkParser;
but in
https://svn.a
Hello Reinhard!!!
that is *great* news!!! I'm going to checkout the branch to see new
APIs, you have the full support from my side!
Thanks a lot for taking care of it!
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www
As I mentioned several times I think we should polish the pipeline API
before we do our first beta release of Cocoon 3. Especially the enforced
resutl type "OutputStream" and the exception handling need some
improvements.
For that purpose I created a branch "c3-pipeline-api-refactoring" in o
