[c3] Pipeline API refactoring
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 our whiteboard (https://svn.apache.org/repos/asf/cocoon/whiteboard/c3-pipeline-api-refactoring/) so that our discussions don't become too theoretical ;-) That branch only contains a minimum set of classes so that we see the effects of a proposed change on real code but don't have to change the whole codebase just for some examples that might be thrown away. Steven and I plan to continue our work some time next week. We will commit our changes then and explain them on the mailing list for further discussions. -- Reinhard Pötz Founder Managing Director, Indoqa and Deepsearch http://www.indoqa.com/people/reinhard-poetz.html Member of the Apache Software Foundation Apache Cocoon Committer, PMC member reinh...@apache.org Furthermore, I think Oracle has to honor the JSPA agreement. http://s.apache.org/JCPIsDead http://s.apache.org/tck-trap
Re: [c3] Pipeline API refactoring
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.99soft.org/ On Thu, Jan 19, 2012 at 9:09 AM, Reinhard Pötz reinh...@apache.org wrote: 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 our whiteboard (https://svn.apache.org/repos/asf/cocoon/whiteboard/c3-pipeline-api-refactoring/) so that our discussions don't become too theoretical ;-) That branch only contains a minimum set of classes so that we see the effects of a proposed change on real code but don't have to change the whole codebase just for some examples that might be thrown away. Steven and I plan to continue our work some time next week. We will commit our changes then and explain them on the mailing list for further discussions. -- Reinhard Pötz Founder Managing Director, Indoqa and Deepsearch http://www.indoqa.com/people/reinhard-poetz.html Member of the Apache Software Foundation Apache Cocoon Committer, PMC member reinh...@apache.org Furthermore, I think Oracle has to honor the JSPA agreement. http://s.apache.org/JCPIsDead http://s.apache.org/tck-trap
[c3] XincludeTransformer.java weirdness
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.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-sax/src/main/java/org/apache/cocoon/sax/xpointer/ There is no such classes. I do not understand since we can build with cli without problems. In eclipse I can fix the project setup by adding the cocoon-sax beta jar to the classpath. However that is the same jar as the project, which does not make sense at all. Somebody has an idea? salu2 -- Thorsten Scherlerscherler.at.gmail.com codeBusters S.L. - web based systems consulting, training and solutions http://www.codebusters.es/
Re: [c3] XincludeTransformer.java weirdness
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.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.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-sax/src/main/java/org/apache/cocoon/sax/xpointer/ There is no such classes. I do not understand since we can build with cli without problems. In eclipse I can fix the project setup by adding the cocoon-sax beta jar to the classpath. However that is the same jar as the project, which does not make sense at all. Somebody has an idea? salu2
Re: [c3] XincludeTransformer.java weirdness
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. I thought it must have something like that. Thanks again for pointing out!. salu2 Jos On 01/19/2012 10:56 AM, Thorsten Scherler wrote: 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.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-sax/src/main/java/org/apache/cocoon/sax/xpointer/ There is no such classes. I do not understand since we can build with cli without problems. In eclipse I can fix the project setup by adding the cocoon-sax beta jar to the classpath. However that is the same jar as the project, which does not make sense at all. Somebody has an idea? salu2 -- Thorsten Scherlerscherler.at.gmail.com codeBusters S.L. - web based systems consulting, training and solutions http://www.codebusters.es/
Re: [c3] XincludeTransformer.java weirdness
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, Jan 19, 2012 at 11:25 AM, Thorsten Scherler scher...@gmail.com wrote: 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. I thought it must have something like that. Thanks again for pointing out!. salu2 Jos On 01/19/2012 10:56 AM, Thorsten Scherler wrote: 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.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-sax/src/main/java/org/apache/cocoon/sax/xpointer/ There is no such classes. I do not understand since we can build with cli without problems. In eclipse I can fix the project setup by adding the cocoon-sax beta jar to the classpath. However that is the same jar as the project, which does not make sense at all. Somebody has an idea? salu2 -- Thorsten Scherlerscherler.at.gmail.com codeBusters S.L. - web based systems consulting, training and solutions http://www.codebusters.es/
