[jira] Assigned: (COCOON-2277) NPE in DynamicURLStreamHandlerFactory (Cocoon JNET)
[ https://issues.apache.org/jira/browse/COCOON-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz reassigned COCOON-2277: -- Assignee: Reinhard Poetz NPE in DynamicURLStreamHandlerFactory (Cocoon JNET) --- Key: COCOON-2277 URL: https://issues.apache.org/jira/browse/COCOON-2277 Project: Cocoon Issue Type: Bug Components: * Cocoon Core, - Servlet service framework Affects Versions: 2.2-dev (Current SVN) Reporter: Gabriel Gruber Assignee: Reinhard Poetz Priority: Critical From time to time after more heavy of our cocoon 2.2 based application (which is not yet in production) I am getting this exception from cocoon jnet. after this exception occurs we have to restart the web application as this exception keeps coming and noone can do anything with the webapp java.lang.NullPointerException java.util.LinkedList.remove(LinkedList.java:646) java.util.LinkedList.remove(LinkedList.java:360) org.apache.cocoon.jnet.DynamicURLStreamHandlerFactory.pop(DynamicURLStreamHandlerFactory.java:30) org.apache.cocoon.jnet.URLHandlerFactoryCollector.popUrlHandlerFactories(URLHandlerFactoryCollector.java:57) org.apache.cocoon.jnet.URLHandlerFactoryCollector.installURLHandlers(URLHandlerFactoryCollector.java:39) sun.reflect.GeneratedMethodAccessor516.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:585) org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:627) org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:616) org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:64) org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89) org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) $Proxy34.service(Unknown Source) org.apache.cocoon.servletservice.ServletServiceContext$PathDispatcher.forward(ServletServiceContext.java:481) org.apache.cocoon.servletservice.ServletServiceContext$PathDispatcher.forward(ServletServiceContext.java:455) org.apache.cocoon.servletservice.spring.ServletFactoryBean$ServiceInterceptor.invoke(ServletFactoryBean.java:245) org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) $Proxy94.service(Unknown Source) org.apache.cocoon.servletservice.DispatcherServlet.service(DispatcherServlet.java:106) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.apache.cocoon.servlet.multipart.MultipartFilter.doFilter(MultipartFilter.java:131) *NOTE* that another open source project reported similar problems: http://jira.dspace.org/jira/browse/DS-253?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON-2277) NPE in DynamicURLStreamHandlerFactory (Cocoon JNET)
[ https://issues.apache.org/jira/browse/COCOON-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON-2277. -- Resolution: Fixed Patch applied as suggest by me and confirmed by others. NPE in DynamicURLStreamHandlerFactory (Cocoon JNET) --- Key: COCOON-2277 URL: https://issues.apache.org/jira/browse/COCOON-2277 Project: Cocoon Issue Type: Bug Components: * Cocoon Core, - Servlet service framework Affects Versions: 2.2-dev (Current SVN) Reporter: Gabriel Gruber Assignee: Reinhard Poetz Priority: Critical From time to time after more heavy of our cocoon 2.2 based application (which is not yet in production) I am getting this exception from cocoon jnet. after this exception occurs we have to restart the web application as this exception keeps coming and noone can do anything with the webapp java.lang.NullPointerException java.util.LinkedList.remove(LinkedList.java:646) java.util.LinkedList.remove(LinkedList.java:360) org.apache.cocoon.jnet.DynamicURLStreamHandlerFactory.pop(DynamicURLStreamHandlerFactory.java:30) org.apache.cocoon.jnet.URLHandlerFactoryCollector.popUrlHandlerFactories(URLHandlerFactoryCollector.java:57) org.apache.cocoon.jnet.URLHandlerFactoryCollector.installURLHandlers(URLHandlerFactoryCollector.java:39) sun.reflect.GeneratedMethodAccessor516.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) java.lang.reflect.Method.invoke(Method.java:585) org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:627) org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:616) org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:64) org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89) org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) $Proxy34.service(Unknown Source) org.apache.cocoon.servletservice.ServletServiceContext$PathDispatcher.forward(ServletServiceContext.java:481) org.apache.cocoon.servletservice.ServletServiceContext$PathDispatcher.forward(ServletServiceContext.java:455) org.apache.cocoon.servletservice.spring.ServletFactoryBean$ServiceInterceptor.invoke(ServletFactoryBean.java:245) org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) $Proxy94.service(Unknown Source) org.apache.cocoon.servletservice.DispatcherServlet.service(DispatcherServlet.java:106) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.apache.cocoon.servlet.multipart.MultipartFilter.doFilter(MultipartFilter.java:131) *NOTE* that another open source project reported similar problems: http://jira.dspace.org/jira/browse/DS-253?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-47) Conditional GET support
[ https://issues.apache.org/jira/browse/COCOON3-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-47. - Resolution: Fixed Patch applied some time ago. Close the issue. Conditional GET support --- Key: COCOON3-47 URL: https://issues.apache.org/jira/browse/COCOON3-47 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-servlet Reporter: Reinhard Poetz Assignee: Cocoon Developers Team Fix For: 3.0.0-alpha-3 Attachments: ConditionalGetSupport.diff.txt The RequestProcessor supports conditional GET requests but in the case of a 'NOT_MODIFIED response, the pipeline is still executed. That's of course unnecessary and we could save some CPU cycles. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (COCOON3-47) Conditional GET support
[ https://issues.apache.org/jira/browse/COCOON3-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz reassigned COCOON3-47: - Assignee: Reinhard Poetz (was: Cocoon Developers Team) Conditional GET support --- Key: COCOON3-47 URL: https://issues.apache.org/jira/browse/COCOON3-47 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-servlet Reporter: Reinhard Poetz Assignee: Reinhard Poetz Fix For: 3.0.0-alpha-3 Attachments: ConditionalGetSupport.diff.txt The RequestProcessor supports conditional GET requests but in the case of a 'NOT_MODIFIED response, the pipeline is still executed. That's of course unnecessary and we could save some CPU cycles. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-49) Four pom.xml files contain duplicate dependencies or deprecated properties.
[
https://issues.apache.org/jira/browse/COCOON3-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reinhard Poetz closed COCOON3-49.
-
Resolution: Fixed
Fix Version/s: 3.0.0-alpha-2
Patch applied, except removing spring-context from the parent POM.
Four pom.xml files contain duplicate dependencies or deprecated properties.
---
Key: COCOON3-49
URL: https://issues.apache.org/jira/browse/COCOON3-49
Project: Cocoon 3
Issue Type: Bug
Components: cocoon-monitoring, cocoon-profiling, cocoon-sample
Affects Versions: 3.0.0-alpha-3
Reporter: Charles Yates
Assignee: Reinhard Poetz
Priority: Minor
Fix For: 3.0.0-alpha-2
Attachments: patch.txt
cocoon-monitoring/pom.xml, cocoon-profiling/pom.xml, cocoon-sample/pom.xml
and parent/pom.xml have duplicate dependency declarations or use the
deprecated ${pom.artifactId} property. The duplicate dependency declarations
cause fatal build errors when using the latest sonatype m2eclipse plugin
which uses maven 3 (http://m2eclipse.sonatype.org/).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (COCOON3-49) Four pom.xml files contain duplicate dependencies or deprecated properties.
[
https://issues.apache.org/jira/browse/COCOON3-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reinhard Poetz reassigned COCOON3-49:
-
Assignee: Reinhard Poetz (was: Cocoon Developers Team)
Four pom.xml files contain duplicate dependencies or deprecated properties.
---
Key: COCOON3-49
URL: https://issues.apache.org/jira/browse/COCOON3-49
Project: Cocoon 3
Issue Type: Bug
Components: cocoon-monitoring, cocoon-profiling, cocoon-sample
Affects Versions: 3.0.0-alpha-3
Reporter: Charles Yates
Assignee: Reinhard Poetz
Priority: Minor
Fix For: 3.0.0-alpha-2
Attachments: patch.txt
cocoon-monitoring/pom.xml, cocoon-profiling/pom.xml, cocoon-sample/pom.xml
and parent/pom.xml have duplicate dependency declarations or use the
deprecated ${pom.artifactId} property. The duplicate dependency declarations
cause fatal build errors when using the latest sonatype m2eclipse plugin
which uses maven 3 (http://m2eclipse.sonatype.org/).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (COCOON3-49) Four pom.xml files contain duplicate dependencies or deprecated properties.
[
https://issues.apache.org/jira/browse/COCOON3-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12842978#action_12842978
]
Reinhard Poetz edited comment on COCOON3-49 at 3/9/10 9:20 AM:
---
Patch applied, except removing spring-context from the parent POM which broke
my build.
was (Author: reinh...@apache.org):
Patch applied, except removing spring-context from the parent POM.
Four pom.xml files contain duplicate dependencies or deprecated properties.
---
Key: COCOON3-49
URL: https://issues.apache.org/jira/browse/COCOON3-49
Project: Cocoon 3
Issue Type: Bug
Components: cocoon-monitoring, cocoon-profiling, cocoon-sample
Affects Versions: 3.0.0-alpha-3
Reporter: Charles Yates
Assignee: Reinhard Poetz
Priority: Minor
Fix For: 3.0.0-alpha-2
Attachments: patch.txt
cocoon-monitoring/pom.xml, cocoon-profiling/pom.xml, cocoon-sample/pom.xml
and parent/pom.xml have duplicate dependency declarations or use the
deprecated ${pom.artifactId} property. The duplicate dependency declarations
cause fatal build errors when using the latest sonatype m2eclipse plugin
which uses maven 3 (http://m2eclipse.sonatype.org/).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON3-53) Cocoon 3: XMLSerializer caches all
[ https://issues.apache.org/jira/browse/COCOON3-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12842993#action_12842993 ] Reinhard Poetz commented on COCOON3-53: --- Both generators (TermGenerator and WorkspaceProvider) create a SimpleCacheKey. A SimpleCacheKey is always valid and the equals method only checks the passed object is of type SimpleCacheKey. It is used for components that always create the same result if the passed events are the same (i.e. there are no external influences) You should use some other cache key implementation: Have a look at ParameterCacheKey or TimestampCacheKey. Cocoon 3: XMLSerializer caches all -- Key: COCOON3-53 URL: https://issues.apache.org/jira/browse/COCOON3-53 Project: Cocoon 3 Issue Type: Bug Components: cocoon-pipeline Reporter: Jos Snellings After startup, any pipeline/matcher ending in an xml-serializer will produce the output of the first request after server startup, regardless of the url, let alone parameters. So the first xml pipe that is activated produces the expected output. All subsequent calls will echo that output, whatever the url or parameters. It takes a server restart to make a pipeline ending in an xml serializer work again. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON3-53) Cocoon 3: XMLSerializer caches all
[ https://issues.apache.org/jira/browse/COCOON3-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12843002#action_12843002 ] Reinhard Poetz commented on COCOON3-53: --- The cache key has to contain everything that influences the output produced by the generator. I have no idea why HTML serialization makes a difference, but again, the logs should give you some hints. Cocoon 3: XMLSerializer caches all -- Key: COCOON3-53 URL: https://issues.apache.org/jira/browse/COCOON3-53 Project: Cocoon 3 Issue Type: Bug Components: cocoon-pipeline Reporter: Jos Snellings After startup, any pipeline/matcher ending in an xml-serializer will produce the output of the first request after server startup, regardless of the url, let alone parameters. So the first xml pipe that is activated produces the expected output. All subsequent calls will echo that output, whatever the url or parameters. It takes a server restart to make a pipeline ending in an xml serializer work again. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON3-53) Cocoon 3: XMLSerializer caches all
[ https://issues.apache.org/jira/browse/COCOON3-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12842756#action_12842756 ] Reinhard Poetz commented on COCOON3-53: --- I can't reproduce your problem: see #testCachingOfDifferentPipelines() http://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-sample-webapp/src/test/java/org/apache/cocoon/it/CachingOfPipelinesTest.java The pipeline can be found at http://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-sample/src/main/resources/COB-INF/sitemap.xmap, lines 50 - 56. Is my test wrong? Cocoon 3: XMLSerializer caches all -- Key: COCOON3-53 URL: https://issues.apache.org/jira/browse/COCOON3-53 Project: Cocoon 3 Issue Type: Bug Components: cocoon-pipeline Reporter: Jos Snellings After startup, any pipeline/matcher ending in an xml-serializer will produce the output of the first request after server startup, regardless of the url, let alone parameters. So the first xml pipe that is activated produces the expected output. All subsequent calls will echo that output, whatever the url or parameters. It takes a server restart to make a pipeline ending in an xml serializer work again. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Moved: (COCOON3-53) Cocoon 3: XMLSerializer caches all
[ https://issues.apache.org/jira/browse/COCOON3-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz moved COCOON-2287 to COCOON3-53: --- Component/s: (was: * Cocoon Core) cocoon-pipeline Affects version (Component): (was: Parent values: Cocoon Core(10151). ) Urgency: (was: Urgent) Key: COCOON3-53 (was: COCOON-2287) Project: Cocoon 3 (was: Cocoon) Cocoon 3: XMLSerializer caches all -- Key: COCOON3-53 URL: https://issues.apache.org/jira/browse/COCOON3-53 Project: Cocoon 3 Issue Type: Bug Components: cocoon-pipeline Reporter: Jos Snellings After startup, any pipeline/matcher ending in an xml-serializer will produce the output of the first request after server startup, regardless of the url, let alone parameters. So the first xml pipe that is activated produces the expected output. All subsequent calls will echo that output, whatever the url or parameters. It takes a server restart to make a pipeline ending in an xml serializer work again. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (COCOON3-48) Relative access of deeply nested matcher parameters doesn't work
Relative access of deeply nested matcher parameters doesn't work
Key: COCOON3-48
URL: https://issues.apache.org/jira/browse/COCOON3-48
Project: Cocoon 3
Issue Type: Bug
Components: cocoon-sitemap
Affects Versions: 3.0.0-alpha-3
Reporter: Reinhard Poetz
Assignee: Cocoon Developers Team
Following pipeline doesn't work:
map:match wildcard=deep-relative-matcher/{a}
map:match value={jexl:cocoon.request.param_a} equals=1
map:match value={jexl:cocoon.request.param_b} equals=1
map:generate src=sax-pipeline/simple.xml /
map:transform src=sax-pipeline/simple.xslt
map:parameter name=myParam value={map:../../a} /
/map:transform
map:serialize /
/map:match
/map:match
/map:match
I added this pipeline to the cocoon-samples sitemap and an integration test to
org.apache.cocoon.it.MatcherTest#ignored_testDeepRelativeMatcher().
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (COCOON3-3) Provide an XInclude transformer as a PipelineComponent
[ https://issues.apache.org/jira/browse/COCOON3-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz reassigned COCOON3-3: Assignee: Reinhard Poetz (was: Cocoon Developers Team) Provide an XInclude transformer as a PipelineComponent -- Key: COCOON3-3 URL: https://issues.apache.org/jira/browse/COCOON3-3 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-sax Affects Versions: 3.0.0-alpha-1 Reporter: Simone Tripodi Assignee: Reinhard Poetz Priority: Minor Fix For: 3.0.0-alpha-3 Attachments: XInclude.patch, XIncludeTransformer.patch, XIncludeTransformerFixedAndApacheHeaders.patch Oldest versions of cocoon already contain an XInclude transformer, it could be a good starting point: http://svn.eu.apache.org/repos/asf/cocoon/trunk/core/cocoon-pipeline/cocoon-pipeline-components/src/main/java/org/apache/cocoon/transformation/XIncludeTransformer.java XPointer package's dependencies should be reduced to be imported in the new pipeline: http://svn.eu.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/src/java/org/apache/cocoon/components/xpointer An alternative solution could be using xerces2 APIs: http://xerces.apache.org/xerces2-j/faq-xinclude.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-3) Provide an XInclude transformer as a PipelineComponent
[ https://issues.apache.org/jira/browse/COCOON3-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-3. Resolution: Fixed Fix Version/s: (was: 3.0.0-alpha-3) 3.0.0-alpha-2 Patch applied, many thanks Simone! Provide an XInclude transformer as a PipelineComponent -- Key: COCOON3-3 URL: https://issues.apache.org/jira/browse/COCOON3-3 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-sax Affects Versions: 3.0.0-alpha-1 Reporter: Simone Tripodi Assignee: Reinhard Poetz Priority: Minor Fix For: 3.0.0-alpha-2 Attachments: XInclude.patch, XIncludeTransformer.patch, XIncludeTransformerFixedAndApacheHeaders.patch Oldest versions of cocoon already contain an XInclude transformer, it could be a good starting point: http://svn.eu.apache.org/repos/asf/cocoon/trunk/core/cocoon-pipeline/cocoon-pipeline-components/src/main/java/org/apache/cocoon/transformation/XIncludeTransformer.java XPointer package's dependencies should be reduced to be imported in the new pipeline: http://svn.eu.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/src/java/org/apache/cocoon/components/xpointer An alternative solution could be using xerces2 APIs: http://xerces.apache.org/xerces2-j/faq-xinclude.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (COCOON3-47) Conditional GET support
Conditional GET support --- Key: COCOON3-47 URL: https://issues.apache.org/jira/browse/COCOON3-47 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-servlet Reporter: Reinhard Poetz Assignee: Cocoon Developers Team Fix For: 3.0.0-alpha-3 Attachments: ConditionalGetSupport.diff.txt The RequestProcessor supports conditional GET requests but in the case of a 'NOT_MODIFIED response, the pipeline is still executed. That's of course unnecessary and we could save some CPU cycles. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COCOON3-47) Conditional GET support
[ https://issues.apache.org/jira/browse/COCOON3-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz updated COCOON3-47: -- Attachment: ConditionalGetSupport.diff.txt Conditional GET support --- Key: COCOON3-47 URL: https://issues.apache.org/jira/browse/COCOON3-47 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-servlet Reporter: Reinhard Poetz Assignee: Cocoon Developers Team Fix For: 3.0.0-alpha-3 Attachments: ConditionalGetSupport.diff.txt The RequestProcessor supports conditional GET requests but in the case of a 'NOT_MODIFIED response, the pipeline is still executed. That's of course unnecessary and we could save some CPU cycles. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (COCOON3-44) Upgrade to latest version of StringTemplate
Upgrade to latest version of StringTemplate --- Key: COCOON3-44 URL: https://issues.apache.org/jira/browse/COCOON3-44 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-stringtemplate Reporter: Reinhard Poetz Assignee: Cocoon Developers Team Fix For: 3.0.0-alpha-3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (COCOON3-45) Support input types than java.net.URL in the StringTemplateGenerator
Support input types than java.net.URL in the StringTemplateGenerator Key: COCOON3-45 URL: https://issues.apache.org/jira/browse/COCOON3-45 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-stringtemplate Reporter: Reinhard Poetz Assignee: Cocoon Developers Team Fix For: 3.0.0-alpha-3 Possible types are: File, String, InputStream -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-6) The org.apache.cocoon.pipeline.component.sax.XSLTTransformer can be optimized
[ https://issues.apache.org/jira/browse/COCOON3-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-6. Resolution: Fixed Thanks Simone four your work on this next step in order to improve the XSLT transformer. The org.apache.cocoon.pipeline.component.sax.XSLTTransformer can be optimized - Key: COCOON3-6 URL: https://issues.apache.org/jira/browse/COCOON3-6 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-sax Affects Versions: 3.0.0-alpha-2 Reporter: Simone Tripodi Assignee: Reinhard Poetz Priority: Minor Fix For: 3.0.0-alpha-2 Attachments: OptimizedXSLT+xsltcTransformer.patch, XSLTTransformerOptimization.patch Every time the XSLTTransformer#setXMLConsumer method is called, the XSLT is parsed reading the URL source and used to create the javax.xml.transform.sax.TransformerHandler: to be more clear [...] XSLTTransformer xsltTransformer = new XSLTTransformer(getClass().getResource(myXSLT.xsl)); Pipeline pipeline1 = new NonCachingPipeline(); pipeline1.addComponent(new StringGenerator(xy//x)); pipeline1.addComponent(xsltTransformer); pipeline1.addComponent(new XMLSerializer()); pipeline1.setup(System.out); pipeline1.execute(); Pipeline pipeline2 = new NonCachingPipeline(); pipeline2.addComponent(new StringGenerator(zw//z)); pipeline2.addComponent(xsltTransformer); == the URL pointed by getClass().getResource(myXSLT.xsl) will be parsed again!!! pipeline2.addComponent(new XMLSerializer()); pipeline2.setup(System.out); pipeline2.execute(); As a quick solution we can store the Template to build the transformer handler objects in a static hashmap, but in the future we should introduce stores. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-41) Cocoon-monitoring, statistics module
[
https://issues.apache.org/jira/browse/COCOON3-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reinhard Poetz closed COCOON3-41.
-
Resolution: Fixed
Assignee: Reinhard Poetz (was: Cocoon Developers Team)
Many thanks for your work!
Cocoon-monitoring, statistics module
Key: COCOON3-41
URL: https://issues.apache.org/jira/browse/COCOON3-41
Project: Cocoon 3
Issue Type: Task
Components: cocoon-monitoring
Reporter: Dariusz Łuksza
Assignee: Reinhard Poetz
Fix For: 3.0.0-alpha-2
Attachments: statistics-StatisticsCollector.patch
This module should expose statistics about use of:
* pipeline
* cache's
* single file ('pipeline matches')
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (COCOON3-3) Provide an XInclude transformer as a PipelineComponent
[ https://issues.apache.org/jira/browse/COCOON3-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz updated COCOON3-3: - Fix Version/s: (was: 3.0.0-alpha-2) 3.0.0-alpha-3 Affects Version/s: (was: 3.0.0-alpha-2) 3.0.0-alpha-1 Provide an XInclude transformer as a PipelineComponent -- Key: COCOON3-3 URL: https://issues.apache.org/jira/browse/COCOON3-3 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-sax Affects Versions: 3.0.0-alpha-1 Reporter: Simone Tripodi Assignee: Cocoon Developers Team Priority: Minor Fix For: 3.0.0-alpha-3 Attachments: XInclude.patch, XIncludeTransformerFixedAndApacheHeaders.patch Oldest versions of cocoon already contain an XInclude transformer, it could be a good starting point: http://svn.eu.apache.org/repos/asf/cocoon/trunk/core/cocoon-pipeline/cocoon-pipeline-components/src/main/java/org/apache/cocoon/transformation/XIncludeTransformer.java XPointer package's dependencies should be reduced to be imported in the new pipeline: http://svn.eu.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/src/java/org/apache/cocoon/components/xpointer An alternative solution could be using xerces2 APIs: http://xerces.apache.org/xerces2-j/faq-xinclude.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COCOON3-8) Add a Digester processor Finisher for the Pipeline
[ https://issues.apache.org/jira/browse/COCOON3-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz updated COCOON3-8: - Fix Version/s: (was: 3.0.0-alpha-2) 3.0.0-alpha-3 Affects Version/s: (was: 3.0.0-alpha-2) Add a Digester processor Finisher for the Pipeline -- Key: COCOON3-8 URL: https://issues.apache.org/jira/browse/COCOON3-8 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-optional Reporter: Simone Tripodi Assignee: Cocoon Developers Team Priority: Minor Fix For: 3.0.0-alpha-3 Attachments: DigesterFinisher.patch, DigesterFinisherWithBetwixtTest.patch The Pipeline is useful not only to stream XML to an OutputStream, but also to implement efficient XML processors; an hypothetical scenario can be an XML - DB pipeline, with intermediary transformations and validation. The Apache community owns an extraordinary XML Processor called Digester - informations can be found on http://commons.apache.org/digester The Digester itself is an org.xml.sax.helpers.DefaultHandler extension, so it can be easily integrated in the pipeline's flow. It have to be a finisher, and not an intermediary component, because the Digester is focused on XML - Java Objects, so it doesn't make sense transforming XML to POJOs and than XML again -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-33) Cocoon-monitoring logging reconfiguration
[ https://issues.apache.org/jira/browse/COCOON3-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-33. - Resolution: Fixed Many thanks, patch applied. Cocoon-monitoring logging reconfiguration - Key: COCOON3-33 URL: https://issues.apache.org/jira/browse/COCOON3-33 Project: Cocoon 3 Issue Type: Task Components: cocoon-monitoring Reporter: Dariusz Łuksza Assignee: Reinhard Poetz Fix For: 3.0.0-alpha-2 Attachments: cocoon-reconfiguration.patch, new-cocoon-monitoring-module.patch, new-cocoon-monitoring-module2.patch Setup new C3 module cocoon-monitoring and implement support for logging reconfiguration via JMX. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COCOON3-35) Support access to URLs that require authentication.
[ https://issues.apache.org/jira/browse/COCOON3-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz updated COCOON3-35: -- Fix Version/s: (was: 3.0.0-alpha-2) 3.0.0-alpha-3 Affects Version/s: (was: 3.0.0-alpha-1) Moving it to alpha-3 - don't know if I have enough time to provide the integration test. Support access to URLs that require authentication. --- Key: COCOON3-35 URL: https://issues.apache.org/jira/browse/COCOON3-35 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-sax, cocoon-stax, cocoon-stringtemplate Reporter: Steven Dolg Assignee: Cocoon Developers Team Priority: Minor Fix For: 3.0.0-alpha-3 Attachments: authentication.patch, authentication2.patch Currently our pipeline components cannot access URLs that require authentication. While it is possible to create specialized versions of each component and add authentication there, it shouldn't be too difficult to support this feature in every pipeline component we currently have. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (COCOON3-26) Integrate the cocoon subproject 'cocoon-xml'
[ https://issues.apache.org/jira/browse/COCOON3-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz reassigned COCOON3-26: - Assignee: Reinhard Poetz (was: Cocoon Developers Team) Integrate the cocoon subproject 'cocoon-xml' Key: COCOON3-26 URL: https://issues.apache.org/jira/browse/COCOON3-26 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-sax Reporter: Reinhard Poetz Assignee: Reinhard Poetz Fix For: 3.0.0-alpha-2 Attachments: cocoon-xml.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-26) Integrate the cocoon subproject 'cocoon-xml'
[ https://issues.apache.org/jira/browse/COCOON3-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-26. - Resolution: Fixed Applied long time ago. Integrate the cocoon subproject 'cocoon-xml' Key: COCOON3-26 URL: https://issues.apache.org/jira/browse/COCOON3-26 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-sax Reporter: Reinhard Poetz Assignee: Reinhard Poetz Fix For: 3.0.0-alpha-2 Attachments: cocoon-xml.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (COCOON3-6) The org.apache.cocoon.pipeline.component.sax.XSLTTransformer can be optimized
[ https://issues.apache.org/jira/browse/COCOON3-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz reassigned COCOON3-6: Assignee: Reinhard Poetz (was: Cocoon Developers Team) The org.apache.cocoon.pipeline.component.sax.XSLTTransformer can be optimized - Key: COCOON3-6 URL: https://issues.apache.org/jira/browse/COCOON3-6 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-sax Affects Versions: 3.0.0-alpha-2 Reporter: Simone Tripodi Assignee: Reinhard Poetz Priority: Minor Fix For: 3.0.0-alpha-2 Attachments: OptimizedXSLT+xsltcTransformer.patch, XSLTTransformerOptimization.patch Every time the XSLTTransformer#setXMLConsumer method is called, the XSLT is parsed reading the URL source and used to create the javax.xml.transform.sax.TransformerHandler: to be more clear [...] XSLTTransformer xsltTransformer = new XSLTTransformer(getClass().getResource(myXSLT.xsl)); Pipeline pipeline1 = new NonCachingPipeline(); pipeline1.addComponent(new StringGenerator(xy//x)); pipeline1.addComponent(xsltTransformer); pipeline1.addComponent(new XMLSerializer()); pipeline1.setup(System.out); pipeline1.execute(); Pipeline pipeline2 = new NonCachingPipeline(); pipeline2.addComponent(new StringGenerator(zw//z)); pipeline2.addComponent(xsltTransformer); == the URL pointed by getClass().getResource(myXSLT.xsl) will be parsed again!!! pipeline2.addComponent(new XMLSerializer()); pipeline2.setup(System.out); pipeline2.execute(); As a quick solution we can store the Template to build the transformer handler objects in a static hashmap, but in the future we should introduce stores. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON3-43) Provide a Consumer that interacts with solr
[ https://issues.apache.org/jira/browse/COCOON3-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12765956#action_12765956 ] Reinhard Poetz commented on COCOON3-43: --- The SolrConsumer inherits from AbstractSAXTransformer now and was able to remove a lot of delegation code which is covered by the abstract transformer. Could you please cross-check if this works for you too? Thanks! Provide a Consumer that interacts with solr --- Key: COCOON3-43 URL: https://issues.apache.org/jira/browse/COCOON3-43 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-sax Reporter: Bertil Chapuis Attachments: SolrConsumer.patch In solr, the org.apache.solr.handler.XMLLoader class allows to save xml documents in a solr index. In the same way, cocoon could provides a SAXConsumer that lets save documents in a solr index. The input document should respect a structure as this one: docs doc field name=... boost=../field /doc ... /docs -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON3-43) Provide a Consumer that interacts with solr
[ https://issues.apache.org/jira/browse/COCOON3-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12765970#action_12765970 ] Reinhard Poetz commented on COCOON3-43: --- Thanks, I removed the interface. Provide a Consumer that interacts with solr --- Key: COCOON3-43 URL: https://issues.apache.org/jira/browse/COCOON3-43 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-sax Reporter: Bertil Chapuis Attachments: SolrConsumer.patch In solr, the org.apache.solr.handler.XMLLoader class allows to save xml documents in a solr index. In the same way, cocoon could provides a SAXConsumer that lets save documents in a solr index. The input document should respect a structure as this one: docs doc field name=... boost=../field /doc ... /docs -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON-2265) Cannot use cocoon-servlet-service-impl 1.2.0 because java.net.MalformedURLException: Could not resolve blockcontext:/...
[
https://issues.apache.org/jira/browse/COCOON-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12759142#action_12759142
]
Reinhard Poetz commented on COCOON-2265:
Although we don't publish to any snapshot repository you can download it
directly from our CI server:
http://vmbuild.apache.org/continuum/workingCopy.action?projectId=51projectName=Apache+Cocoon+%5Bbuild+root%5DuserDirectory=core/cocoon-xml/cocoon-xml-resolver/targetfile=cocoon-xml-resolver-1.1.0-SNAPSHOT.jar
Cannot use cocoon-servlet-service-impl 1.2.0 because
java.net.MalformedURLException: Could not resolve blockcontext:/...
Key: COCOON-2265
URL: https://issues.apache.org/jira/browse/COCOON-2265
Project: Cocoon
Issue Type: Bug
Components: - Servlet service framework
Affects Versions: 2.2, 2.2-dev (Current SVN)
Reporter: Mark Diggory
Attachments: test.zip
The following issue occurs with the blockcontext URL when trying to use
cocoon-servlet-service-impl 1.2.0 and mounting a servlet using the default
architype with this dependency added. I am including an example project for
others to test this against.
I am trying to replicate this in a test example is we are having sever
difficulties using 1.2.0 and most specifically using
org.apache.cocoon.sitemap.SitemapServlet in our Cocoon project located here..,
http://jira.dspace.org/jira/browse/DS-253
Here we were able to alleviate
https://issues.apache.org/jira/browse/COCOON-2217, by upgrading to 1.2.0, but
it is causing other problems now.
I am including a new example multimodule project that replicates this. To
execute this project do:
cd test
mvn package install
to execute the first application
cd test-original-webapp
mvn jetty:run
this application should run without issues
to execute the second modified webapplication do:
cd ../test-new-webapp
mvn jetty:run
It is comprised of two example block/webapp pairs
test/test-original-block
test/test-original-webapp
The above example was generated off the cocoon archetypes, in needed to be
altered to adjust for the problem identified in
http://www.nabble.com/Creating-a-parent-POM-td18173518.html
I corrected for this by adding the maven-war-plugin as a plugin in
test/pom.xml, otherwise it is unaltered accept to insert test-original-block
in test-original-webapp. This example works but uses:
org.apache.cocoon:cocoon-servlet-service-impl:1.0.0
The next example is generated the same way but adds dependencies to upgrade
the block to use org.apache.cocoon:cocoon-servlet-service-impl:1.2.0
test/test-new-block
test/test-new-webapp
But I needed to also add an explicit addition of the dependency:
org.apache.excalibur.components:excalibur-sourceresolve:2.2.3 to correct for
the following problem as well...
2009-08-22 17:25:03.216::WARN: Failed startup of context
org.mortbay.jetty.plugin.jetty6pluginwebappcont...@e696f9{/,/Users/mdiggory/test-works/test-new-webapp/target/test-new-webapp-1.0}
org.springframework.beans.factory.BeanDefinitionStoreException: Unable to
read Avalon configuration from 'resource://org/apache/cocoon/cocoon.xconf'.;
nested exception is
org.apache.avalon.framework.configuration.ConfigurationException: Unable to
create class for component with role
org.apache.cocoon.generation.Generator/imagedirectory with class:
org.apache.cocoon.generation.ImageDirectoryGenerator
at
org.apache.cocoon.core.container.spring.avalon.BridgeElementParser.parse(BridgeElementParser.java:86)
...
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.avalon.framework.configuration.ConfigurationException:
Unable to create class for component with role
org.apache.cocoon.generation.Generator/imagedirectory with class:
org.apache.cocoon.generation.ImageDirectoryGenerator
at
org.apache.cocoon.core.container.spring.avalon.BridgeElementParser.createConfig(BridgeElementParser.java:216)
... 58 more
Caused by: java.lang.NoClassDefFoundError:
org/apache/excalibur/source/SourceException
at java.lang.Class.forName0(Native Method)
at
org.apache.cocoon.core.container.spring.avalon.BridgeElementParser.createConfig(BridgeElementParser.java:207)
... 60 more
2009-08-22 17:25:03.228::WARN: Nested in
org.springframework.beans.factory.BeanDefinitionStoreException: Unable to
read Avalon configuration from 'resource://org/apache/cocoon/cocoon.xconf'.;
nested exception is
org.apache.avalon.framework.configuration.ConfigurationException: Unable to
create class for component with role
org.apache.cocoon.generation.Generator/imagedirectory with class:
org.apache.cocoon.generation.ImageDirectoryGenerator
[jira] Closed: (COCOON3-39) Cocoon-monitoring cache overview
[ https://issues.apache.org/jira/browse/COCOON3-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-39. - Resolution: Fixed Patch applied Cocoon-monitoring cache overview Key: COCOON3-39 URL: https://issues.apache.org/jira/browse/COCOON3-39 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-monitoring Reporter: Dariusz Łuksza Assignee: Reinhard Poetz Fix For: 3.0.0-alpha-2 Attachments: cache-overview-all.patch, cache-overview-all2.patch, cache-overview-doc.patch, cache-overview-part1.patch, cache-overview-part2-burst-actions.patch, cache-overview-part3-cache-entrys.patch This milestone of my GSoC project I'll divide in to thee smaller tasks: 1. General overview of configured caches with base functions like: - clearing whole cache - getting list of cached keys - removing single key from cache - getting size of cache 2. Getting list of all CacheKey's and expose them in some kind of logical order on JXM tree 3. Add additional operation and information to every CacheKey like: - clearing cache value - editing cache value - reloading cache value - getting time of creation - getting expires time, if any -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON-2265) Cannot use cocoon-servlet-service-impl 1.2.0 because java.net.MalformedURLException: Could not resolve blockcontext:/...
[
https://issues.apache.org/jira/browse/COCOON-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12749965#action_12749965
]
Reinhard Poetz commented on COCOON-2265:
I see. Can you try to use a SNAPSHOT version of cocoon-xml-resolver from trunk
and report back if this solves your problem?
Cannot use cocoon-servlet-service-impl 1.2.0 because
java.net.MalformedURLException: Could not resolve blockcontext:/...
Key: COCOON-2265
URL: https://issues.apache.org/jira/browse/COCOON-2265
Project: Cocoon
Issue Type: Bug
Components: - Servlet service framework
Affects Versions: 2.2, 2.2-dev (Current SVN)
Reporter: Mark Diggory
Attachments: test.zip
The following issue occurs with the blockcontext URL when trying to use
cocoon-servlet-service-impl 1.2.0 and mounting a servlet using the default
architype with this dependency added. I am including an example project for
others to test this against.
I am trying to replicate this in a test example is we are having sever
difficulties using 1.2.0 and most specifically using
org.apache.cocoon.sitemap.SitemapServlet in our Cocoon project located here..,
http://jira.dspace.org/jira/browse/DS-253
Here we were able to alleviate
https://issues.apache.org/jira/browse/COCOON-2217, by upgrading to 1.2.0, but
it is causing other problems now.
I am including a new example multimodule project that replicates this. To
execute this project do:
cd test
mvn package install
to execute the first application
cd test-original-webapp
mvn jetty:run
this application should run without issues
to execute the second modified webapplication do:
cd ../test-new-webapp
mvn jetty:run
It is comprised of two example block/webapp pairs
test/test-original-block
test/test-original-webapp
The above example was generated off the cocoon archetypes, in needed to be
altered to adjust for the problem identified in
http://www.nabble.com/Creating-a-parent-POM-td18173518.html
I corrected for this by adding the maven-war-plugin as a plugin in
test/pom.xml, otherwise it is unaltered accept to insert test-original-block
in test-original-webapp. This example works but uses:
org.apache.cocoon:cocoon-servlet-service-impl:1.0.0
The next example is generated the same way but adds dependencies to upgrade
the block to use org.apache.cocoon:cocoon-servlet-service-impl:1.2.0
test/test-new-block
test/test-new-webapp
But I needed to also add an explicit addition of the dependency:
org.apache.excalibur.components:excalibur-sourceresolve:2.2.3 to correct for
the following problem as well...
2009-08-22 17:25:03.216::WARN: Failed startup of context
org.mortbay.jetty.plugin.jetty6pluginwebappcont...@e696f9{/,/Users/mdiggory/test-works/test-new-webapp/target/test-new-webapp-1.0}
org.springframework.beans.factory.BeanDefinitionStoreException: Unable to
read Avalon configuration from 'resource://org/apache/cocoon/cocoon.xconf'.;
nested exception is
org.apache.avalon.framework.configuration.ConfigurationException: Unable to
create class for component with role
org.apache.cocoon.generation.Generator/imagedirectory with class:
org.apache.cocoon.generation.ImageDirectoryGenerator
at
org.apache.cocoon.core.container.spring.avalon.BridgeElementParser.parse(BridgeElementParser.java:86)
...
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.avalon.framework.configuration.ConfigurationException:
Unable to create class for component with role
org.apache.cocoon.generation.Generator/imagedirectory with class:
org.apache.cocoon.generation.ImageDirectoryGenerator
at
org.apache.cocoon.core.container.spring.avalon.BridgeElementParser.createConfig(BridgeElementParser.java:216)
... 58 more
Caused by: java.lang.NoClassDefFoundError:
org/apache/excalibur/source/SourceException
at java.lang.Class.forName0(Native Method)
at
org.apache.cocoon.core.container.spring.avalon.BridgeElementParser.createConfig(BridgeElementParser.java:207)
... 60 more
2009-08-22 17:25:03.228::WARN: Nested in
org.springframework.beans.factory.BeanDefinitionStoreException: Unable to
read Avalon configuration from 'resource://org/apache/cocoon/cocoon.xconf'.;
nested exception is
org.apache.avalon.framework.configuration.ConfigurationException: Unable to
create class for component with role
org.apache.cocoon.generation.Generator/imagedirectory with class:
org.apache.cocoon.generation.ImageDirectoryGenerator:
java.lang.NoClassDefFoundError: org/apache/excalibur/source/SourceException
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:164
[jira] Updated: (COCOON3-33) Cocoon-monitoring logging reconfiguration
[ https://issues.apache.org/jira/browse/COCOON3-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz updated COCOON3-33: -- Component/s: (was: cocoon-optional) cocoon-monitoring Cocoon-monitoring logging reconfiguration - Key: COCOON3-33 URL: https://issues.apache.org/jira/browse/COCOON3-33 Project: Cocoon 3 Issue Type: Task Components: cocoon-monitoring Reporter: Dariusz Łuksza Assignee: Reinhard Poetz Fix For: 3.0.0-alpha-2 Attachments: cocoon-reconfiguration.patch, new-cocoon-monitoring-module.patch, new-cocoon-monitoring-module2.patch Setup new C3 module cocoon-monitoring and implement support for logging reconfiguration via JMX. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-40) Final cocoon-profiling patch
[ https://issues.apache.org/jira/browse/COCOON3-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-40. - Resolution: Fixed Final cocoon-profiling patch Key: COCOON3-40 URL: https://issues.apache.org/jira/browse/COCOON3-40 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-optional Reporter: Christoph Leiter Assignee: Reinhard Poetz Priority: Minor Attachments: cocoon-profiling-090821.patch, cocoon-profiling.patch, cocoon-profiling.zip I'll attach the cocoon-profiling patch and the binary files as a zip archive. Please comment if there are any problems with it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COCOON3-38) Cocoon-monitoring base information about Servlet-Services
[ https://issues.apache.org/jira/browse/COCOON3-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz updated COCOON3-38: -- Component/s: (was: cocoon-optional) cocoon-monitoring Cocoon-monitoring base information about Servlet-Services - Key: COCOON3-38 URL: https://issues.apache.org/jira/browse/COCOON3-38 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-monitoring Affects Versions: 3.0.0-alpha-2 Reporter: Dariusz Łuksza Assignee: Reinhard Poetz Priority: Minor Fix For: 3.0.0-alpha-2 Attachments: cocoon-servlet-srvices-impl-connections.patch, servlet-services-doc.patch, servlet-services-doc1.patch, servlet-services-monitor.patch, servlet-services-monitor1.patch, servlet-services-monitor2.patch Add ability of sharing base information about Servlet-Services like points of mount or connections. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COCOON3-39) Cocoon-monitoring cache overview
[ https://issues.apache.org/jira/browse/COCOON3-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz updated COCOON3-39: -- Component/s: (was: cocoon-optional) cocoon-monitoring Cocoon-monitoring cache overview Key: COCOON3-39 URL: https://issues.apache.org/jira/browse/COCOON3-39 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-monitoring Reporter: Dariusz Łuksza Assignee: Reinhard Poetz Attachments: cache-overview-all.patch, cache-overview-all2.patch, cache-overview-doc.patch, cache-overview-part1.patch, cache-overview-part2-burst-actions.patch, cache-overview-part3-cache-entrys.patch This milestone of my GSoC project I'll divide in to thee smaller tasks: 1. General overview of configured caches with base functions like: - clearing whole cache - getting list of cached keys - removing single key from cache - getting size of cache 2. Getting list of all CacheKey's and expose them in some kind of logical order on JXM tree 3. Add additional operation and information to every CacheKey like: - clearing cache value - editing cache value - reloading cache value - getting time of creation - getting expires time, if any -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-19) [PATCH] stax-sax converter
[ https://issues.apache.org/jira/browse/COCOON3-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-19. - Resolution: Fixed [PATCH] stax-sax converter -- Key: COCOON3-19 URL: https://issues.apache.org/jira/browse/COCOON3-19 Project: Cocoon 3 Issue Type: Sub-task Components: cocoon-stax Reporter: Andreas Pieber Assignee: Reinhard Poetz Fix For: 3.0.0-alpha-2 Attachments: cocoon-stax-license.patch, cocooon-stax-converter.patch We experimented with wrappers to add SAX-components to StAX pipelines and with Adapters between StAX pipelines and SAX pipelines. IMO they work quite fine :) The problem with this patch is that it relies on the stax-utils project. Most classes in o.a.c.stax.converter.util are redistrubuted from the stax-utils (https://stax-utils.dev.java.net/) project. This was required since there's an architectural issue so that stax-utils can not be used directly as reference. I posted at the stax-utils dev mailing list two weeks ago, if they could make some of their methods protected instead of private so that we could resolve this issue, but I did not receive an answer. I created a seperated issue for this problem since there's the opened question of how to mark the redistributed classes from the stax-utils project. I think Reinhard know ways of how to resolve this problem :) I created this issue as an subtask of COCOON3-18 since first the patch of COCOON3-18 have to be applied before this patch could be used. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COCOON3-41) Cocoon-monitoring, statistics module
[
https://issues.apache.org/jira/browse/COCOON3-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reinhard Poetz updated COCOON3-41:
--
Component/s: (was: cocoon-optional)
cocoon-monitoring
Affects Version/s: 3.0.0-alpha-2
Cocoon-monitoring, statistics module
Key: COCOON3-41
URL: https://issues.apache.org/jira/browse/COCOON3-41
Project: Cocoon 3
Issue Type: Task
Components: cocoon-monitoring
Reporter: Dariusz Łuksza
Assignee: Cocoon Developers Team
Fix For: 3.0.0-alpha-2
Attachments: statistics-StatisticsCollector.patch
This module should expose statistics about use of:
* pipeline
* cache's
* single file ('pipeline matches')
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (COCOON3-41) Cocoon-monitoring, statistics module
[
https://issues.apache.org/jira/browse/COCOON3-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reinhard Poetz updated COCOON3-41:
--
Fix Version/s: 3.0.0-alpha-2
Affects Version/s: (was: 3.0.0-alpha-2)
Cocoon-monitoring, statistics module
Key: COCOON3-41
URL: https://issues.apache.org/jira/browse/COCOON3-41
Project: Cocoon 3
Issue Type: Task
Components: cocoon-monitoring
Reporter: Dariusz Łuksza
Assignee: Cocoon Developers Team
Fix For: 3.0.0-alpha-2
Attachments: statistics-StatisticsCollector.patch
This module should expose statistics about use of:
* pipeline
* cache's
* single file ('pipeline matches')
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (COCOON3-39) Cocoon-monitoring cache overview
[ https://issues.apache.org/jira/browse/COCOON3-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz updated COCOON3-39: -- Fix Version/s: 3.0.0-alpha-2 Cocoon-monitoring cache overview Key: COCOON3-39 URL: https://issues.apache.org/jira/browse/COCOON3-39 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-monitoring Reporter: Dariusz Łuksza Assignee: Reinhard Poetz Fix For: 3.0.0-alpha-2 Attachments: cache-overview-all.patch, cache-overview-all2.patch, cache-overview-doc.patch, cache-overview-part1.patch, cache-overview-part2-burst-actions.patch, cache-overview-part3-cache-entrys.patch This milestone of my GSoC project I'll divide in to thee smaller tasks: 1. General overview of configured caches with base functions like: - clearing whole cache - getting list of cached keys - removing single key from cache - getting size of cache 2. Getting list of all CacheKey's and expose them in some kind of logical order on JXM tree 3. Add additional operation and information to every CacheKey like: - clearing cache value - editing cache value - reloading cache value - getting time of creation - getting expires time, if any -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-38) Cocoon-monitoring base information about Servlet-Services
[ https://issues.apache.org/jira/browse/COCOON3-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-38. - Resolution: Fixed Cocoon-monitoring base information about Servlet-Services - Key: COCOON3-38 URL: https://issues.apache.org/jira/browse/COCOON3-38 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-monitoring Affects Versions: 3.0.0-alpha-2 Reporter: Dariusz Łuksza Assignee: Reinhard Poetz Priority: Minor Fix For: 3.0.0-alpha-2 Attachments: cocoon-servlet-srvices-impl-connections.patch, servlet-services-doc.patch, servlet-services-doc1.patch, servlet-services-monitor.patch, servlet-services-monitor1.patch, servlet-services-monitor2.patch Add ability of sharing base information about Servlet-Services like points of mount or connections. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON-2265) Cannot use cocoon-servlet-service-impl 1.2.0 because java.net.MalformedURLException: Could not resolve blockcontext:/...
[
https://issues.apache.org/jira/browse/COCOON-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12746689#action_12746689
]
Reinhard Poetz commented on COCOON-2265:
Could you try if adding
listener
descriptionDeclare a context listener that installs all
blocks./description
listener-classorg.apache.cocoon.blockdeployment.BlockDeploymentServletContextListener/listener-class
/listener
to your web.xml solves the problem? AFAICS we missed to add information about
this change to the relevant changes docs. I'm sorry.
And also make sure that your project uses 1.1.0 of the cocoon-block-deployment
module, 2.1.0 of cocoon-spring-configurator and 1.1.0 of cocoon-jnet.
Cannot use cocoon-servlet-service-impl 1.2.0 because
java.net.MalformedURLException: Could not resolve blockcontext:/...
Key: COCOON-2265
URL: https://issues.apache.org/jira/browse/COCOON-2265
Project: Cocoon
Issue Type: Bug
Components: - Servlet service framework
Affects Versions: 2.2, 2.2-dev (Current SVN)
Reporter: Mark Diggory
Attachments: test.zip
The following issue occurs with the blockcontext URL when trying to use
cocoon-servlet-service-impl 1.2.0 and mounting a servlet using the default
architype with this dependency added. I am including an example project for
others to test this against.
I am trying to replicate this in a test example is we are having sever
difficulties using 1.2.0 and most specifically using
org.apache.cocoon.sitemap.SitemapServlet in our Cocoon project located here..,
http://jira.dspace.org/jira/browse/DS-253
Here we were able to alleviate
https://issues.apache.org/jira/browse/COCOON-2217, by upgrading to 1.2.0, but
it is causing other problems now.
I am including a new example multimodule project that replicates this. To
execute this project do:
cd test
mvn package install
to execute the first application
cd test-original-webapp
mvn jetty:run
this application should run without issues
to execute the second modified webapplication do:
cd ../test-new-webapp
mvn jetty:run
It is comprised of two example block/webapp pairs
test/test-original-block
test/test-original-webapp
The above example was generated off the cocoon archetypes, in needed to be
altered to adjust for the problem identified in
http://www.nabble.com/Creating-a-parent-POM-td18173518.html
I corrected for this by adding the maven-war-plugin as a plugin in
test/pom.xml, otherwise it is unaltered accept to insert test-original-block
in test-original-webapp. This example works but uses:
org.apache.cocoon:cocoon-servlet-service-impl:1.0.0
The next example is generated the same way but adds dependencies to upgrade
the block to use org.apache.cocoon:cocoon-servlet-service-impl:1.2.0
test/test-new-block
test/test-new-webapp
But I needed to also add an explicit addition of the dependency:
org.apache.excalibur.components:excalibur-sourceresolve:2.2.3 to correct for
the following problem as well...
2009-08-22 17:25:03.216::WARN: Failed startup of context
org.mortbay.jetty.plugin.jetty6pluginwebappcont...@e696f9{/,/Users/mdiggory/test-works/test-new-webapp/target/test-new-webapp-1.0}
org.springframework.beans.factory.BeanDefinitionStoreException: Unable to
read Avalon configuration from 'resource://org/apache/cocoon/cocoon.xconf'.;
nested exception is
org.apache.avalon.framework.configuration.ConfigurationException: Unable to
create class for component with role
org.apache.cocoon.generation.Generator/imagedirectory with class:
org.apache.cocoon.generation.ImageDirectoryGenerator
at
org.apache.cocoon.core.container.spring.avalon.BridgeElementParser.parse(BridgeElementParser.java:86)
...
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.avalon.framework.configuration.ConfigurationException:
Unable to create class for component with role
org.apache.cocoon.generation.Generator/imagedirectory with class:
org.apache.cocoon.generation.ImageDirectoryGenerator
at
org.apache.cocoon.core.container.spring.avalon.BridgeElementParser.createConfig(BridgeElementParser.java:216)
... 58 more
Caused by: java.lang.NoClassDefFoundError:
org/apache/excalibur/source/SourceException
at java.lang.Class.forName0(Native Method)
at
org.apache.cocoon.core.container.spring.avalon.BridgeElementParser.createConfig(BridgeElementParser.java:207)
... 60 more
2009-08-22 17:25:03.228::WARN: Nested in
org.springframework.beans.factory.BeanDefinitionStoreException: Unable to
read Avalon configuration from 'resource://org/apache/cocoon/cocoon.xconf'.;
nested exception
[jira] Commented: (COCOON3-40) Final cocoon-profiling patch
[ https://issues.apache.org/jira/browse/COCOON3-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12745834#action_12745834 ] Reinhard Poetz commented on COCOON3-40: --- I applied the patch to SVN yesterday. Final cocoon-profiling patch Key: COCOON3-40 URL: https://issues.apache.org/jira/browse/COCOON3-40 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-optional Reporter: Christoph Leiter Assignee: Reinhard Poetz Priority: Minor Attachments: cocoon-profiling.patch, cocoon-profiling.zip I'll attach the cocoon-profiling patch and the binary files as a zip archive. Please comment if there are any problems with it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON3-40) Final cocoon-profiling patch
[ https://issues.apache.org/jira/browse/COCOON3-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12742412#action_12742412 ] Reinhard Poetz commented on COCOON3-40: --- I applied initial fix for the problem with sitemap-node proxies (see rev 803447). This unpacks all proxies but ties the sitemap-node code to Spring which is far from being optimal. I will have to think more about this or maybe somebody else has a better idea. I also applied your patch locally and found one issue: The request for the profling data that were created at first time, fails. Any idea why this happens? Final cocoon-profiling patch Key: COCOON3-40 URL: https://issues.apache.org/jira/browse/COCOON3-40 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-optional Reporter: Christoph Leiter Assignee: Reinhard Poetz Priority: Minor Attachments: cocoon-profiling.patch, cocoon-profiling.zip I'll attach the cocoon-profiling patch and the binary files as a zip archive. Please comment if there are any problems with it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (COCOON3-40) Final cocoon-profiling patch
[ https://issues.apache.org/jira/browse/COCOON3-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz reassigned COCOON3-40: - Assignee: Reinhard Poetz (was: Cocoon Developers Team) Final cocoon-profiling patch Key: COCOON3-40 URL: https://issues.apache.org/jira/browse/COCOON3-40 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-optional Reporter: Christoph Leiter Assignee: Reinhard Poetz Priority: Minor Attachments: cocoon-profiling.patch, cocoon-profiling.zip I'll attach the cocoon-profiling patch and the binary files as a zip archive. Please comment if there are any problems with it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (COCOON3-39) Cocoon-monitoring cache overview
[ https://issues.apache.org/jira/browse/COCOON3-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz reassigned COCOON3-39: - Assignee: Reinhard Poetz (was: Cocoon Developers Team) Cocoon-monitoring cache overview Key: COCOON3-39 URL: https://issues.apache.org/jira/browse/COCOON3-39 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-optional Reporter: Dariusz Łuksza Assignee: Reinhard Poetz Attachments: cache-overview-all.patch, cache-overview-doc.patch, cache-overview-part1.patch, cache-overview-part2-burst-actions.patch, cache-overview-part3-cache-entrys.patch This milestone of my GSoC project I'll divide in to thee smaller tasks: 1. General overview of configured caches with base functions like: - clearing whole cache - getting list of cached keys - removing single key from cache - getting size of cache 2. Getting list of all CacheKey's and expose them in some kind of logical order on JXM tree 3. Add additional operation and information to every CacheKey like: - clearing cache value - editing cache value - reloading cache value - getting time of creation - getting expires time, if any -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON3-38) Cocoon-monitoring base information about Servlet-Services
[ https://issues.apache.org/jira/browse/COCOON3-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12731693#action_12731693 ] Reinhard Poetz commented on COCOON3-38: --- The use of break was of course incorrect. I will also change the bean naming strategy as suggested by you. Cocoon-monitoring base information about Servlet-Services - Key: COCOON3-38 URL: https://issues.apache.org/jira/browse/COCOON3-38 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-optional Affects Versions: 3.0.0-alpha-2 Reporter: Dariusz Łuksza Assignee: Reinhard Poetz Priority: Minor Fix For: 3.0.0-alpha-2 Attachments: cocoon-servlet-srvices-impl-connections.patch, servlet-services-doc.patch, servlet-services-doc1.patch, servlet-services-monitor.patch, servlet-services-monitor1.patch, servlet-services-monitor2.patch Add ability of sharing base information about Servlet-Services like points of mount or connections. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (COCOON3-38) Cocoon-monitoring base information about Servlet-Services
[ https://issues.apache.org/jira/browse/COCOON3-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz reassigned COCOON3-38: - Assignee: Reinhard Poetz (was: Cocoon Developers Team) Cocoon-monitoring base information about Servlet-Services - Key: COCOON3-38 URL: https://issues.apache.org/jira/browse/COCOON3-38 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-optional Affects Versions: 3.0.0-alpha-2 Reporter: Dariusz Łuksza Assignee: Reinhard Poetz Priority: Minor Fix For: 3.0.0-alpha-2 Attachments: cocoon-servlet-srvices-impl-connections.patch, servlet-services-doc.patch, servlet-services-doc1.patch, servlet-services-monitor.patch, servlet-services-monitor1.patch Add ability of sharing base information about Servlet-Services like points of mount or connections. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON3-38) Cocoon-monitoring base information about Servlet-Services
[ https://issues.apache.org/jira/browse/COCOON3-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12731178#action_12731178 ] Reinhard Poetz commented on COCOON3-38: --- I applied servlet-services-monitor1.patch with some minor modifactions: I use a private accessor to get all the connections and their names because otherwise we would need to introduce an dependency on cocoon-servlet-service-impl-1.3.0-SNAPSHOT. As soon as 1.2.1 is released this can be changed (see ServletServiceMonitor). Apart from that I added the mount path to the bean name. Cocoon-monitoring base information about Servlet-Services - Key: COCOON3-38 URL: https://issues.apache.org/jira/browse/COCOON3-38 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-optional Affects Versions: 3.0.0-alpha-2 Reporter: Dariusz Łuksza Assignee: Reinhard Poetz Priority: Minor Fix For: 3.0.0-alpha-2 Attachments: cocoon-servlet-srvices-impl-connections.patch, servlet-services-doc.patch, servlet-services-doc1.patch, servlet-services-monitor.patch, servlet-services-monitor1.patch Add ability of sharing base information about Servlet-Services like points of mount or connections. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COCOON3-38) Cocoon-monitoring base information about Servlet-Services
[ https://issues.apache.org/jira/browse/COCOON3-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz updated COCOON3-38: -- Fix Version/s: 3.0.0-alpha-2 Cocoon-monitoring base information about Servlet-Services - Key: COCOON3-38 URL: https://issues.apache.org/jira/browse/COCOON3-38 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-optional Affects Versions: 3.0.0-alpha-2 Reporter: Dariusz Łuksza Assignee: Cocoon Developers Team Priority: Minor Fix For: 3.0.0-alpha-2 Attachments: cocoon-servlet-srvices-impl-connections.patch, servlet-services-doc.patch, servlet-services-monitor.patch, servlet-services-monitor1.patch Add ability of sharing base information about Servlet-Services like points of mount or connections. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON3-35) Support access to URLs that require authentication.
[ https://issues.apache.org/jira/browse/COCOON3-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12712789#action_12712789 ] Reinhard Poetz commented on COCOON3-35: --- An optional dependency is fine by me too. And replying to your tweet http://twitter.com/BanDoga/status/1915444934 We could add a resource, that is protected by basic HTTP authentication, to our integration test suite. I already have implemented this for another project. I will see what I can do the next days. Support access to URLs that require authentication. --- Key: COCOON3-35 URL: https://issues.apache.org/jira/browse/COCOON3-35 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-sax, cocoon-stax, cocoon-stringtemplate Affects Versions: 3.0.0-alpha-1 Reporter: Steven Dolg Assignee: Cocoon Developers Team Priority: Minor Fix For: 3.0.0-alpha-2 Attachments: authentication.patch, authentication2.patch Currently our pipeline components cannot access URLs that require authentication. While it is possible to create specialized versions of each component and add authentication there, it shouldn't be too difficult to support this feature in every pipeline component we currently have. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-37) cocoon-sample-servlet-service.xml references local file
[ https://issues.apache.org/jira/browse/COCOON3-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-37. - Resolution: Fixed Fix Version/s: 3.0.0-alpha-2 thanks! cocoon-sample-servlet-service.xml references local file --- Key: COCOON3-37 URL: https://issues.apache.org/jira/browse/COCOON3-37 Project: Cocoon 3 Issue Type: Bug Components: cocoon-sample Reporter: Christoph Leiter Assignee: Reinhard Poetz Priority: Trivial Fix For: 3.0.0-alpha-2 cocoon-sample/src/main/resources/META-INF/cocoon/springcocoon-sample-servlet-service.xml declares beans ... xmlns:configurator=http://cocoon.apache.org/schema/configurator; xsi:schemaLocation=... http://cocoon.apache.org/schema/configurator file:///O:/os/cocoon/trunk/subprojects/cocoon-configuration/cocoon-spring-configurator/src/main/resources/org/apache/cocoon/spring/configurator/schema/cocoon-configurator-2.1.0.xsd I don't know what the reasoning for this is, but because the configurator namespace is never used it seems it could be removed altogether. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (COCOON3-37) cocoon-sample-servlet-service.xml references local file
[ https://issues.apache.org/jira/browse/COCOON3-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz reassigned COCOON3-37: - Assignee: Reinhard Poetz (was: Cocoon Developers Team) cocoon-sample-servlet-service.xml references local file --- Key: COCOON3-37 URL: https://issues.apache.org/jira/browse/COCOON3-37 Project: Cocoon 3 Issue Type: Bug Components: cocoon-sample Reporter: Christoph Leiter Assignee: Reinhard Poetz Priority: Trivial Fix For: 3.0.0-alpha-2 cocoon-sample/src/main/resources/META-INF/cocoon/springcocoon-sample-servlet-service.xml declares beans ... xmlns:configurator=http://cocoon.apache.org/schema/configurator; xsi:schemaLocation=... http://cocoon.apache.org/schema/configurator file:///O:/os/cocoon/trunk/subprojects/cocoon-configuration/cocoon-spring-configurator/src/main/resources/org/apache/cocoon/spring/configurator/schema/cocoon-configurator-2.1.0.xsd I don't know what the reasoning for this is, but because the configurator namespace is never used it seems it could be removed altogether. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-36) Initial patch for cocoon-profiling
[ https://issues.apache.org/jira/browse/COCOON3-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-36. - Resolution: Fixed Fix Version/s: 3.0.0-alpha-2 Assignee: Reinhard Poetz (was: Cocoon Developers Team) patch applied. Thanks! (just one minor remark: please don't use tabs. use two spaces for XML indention and four spaces for java sources) Initial patch for cocoon-profiling -- Key: COCOON3-36 URL: https://issues.apache.org/jira/browse/COCOON3-36 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-optional Reporter: Christoph Leiter Assignee: Reinhard Poetz Priority: Minor Fix For: 3.0.0-alpha-2 Attachments: profiling.patch Initial patch to add cocoon-profiling and cocoon-profiling-firebug to cocoon3. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-34) Attaching an aspect to org.apache.cocoon.sitemap.node.Sitemap leads to a ClassCastException
[ https://issues.apache.org/jira/browse/COCOON3-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-34. - Resolution: Fixed Fix Version/s: 3.0.0-alpha-2 Attaching an aspect to org.apache.cocoon.sitemap.node.Sitemap leads to a ClassCastException - Key: COCOON3-34 URL: https://issues.apache.org/jira/browse/COCOON3-34 Project: Cocoon 3 Issue Type: Bug Components: cocoon-sitemap Reporter: Andreas Pinter Assignee: Reinhard Poetz Priority: Minor Fix For: 3.0.0-alpha-2 Attachments: cocoon.log I tried to attach an around-aspect for every node: @Around(execution(* invoke(..)) within(org.apache.cocoon.sitemap.node.*)) This led to a ClassCastException for the first sitemap. (see attached logfile) After excluding sitemap from my aspect, everything works just fine: @Around(execution(* invoke(..)) within(org.apache.cocoon.sitemap.node.* !org.apache.cocoon.sitemap.node.Sitemap)) Tested with cocoon-sample. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON3-35) Support access to URLs that require authentication.
[ https://issues.apache.org/jira/browse/COCOON3-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12707656#action_12707656 ] Reinhard Poetz commented on COCOON3-35: --- The URLSource uses the URLUtils http://svn.apache.org/viewvc/excalibur/trunk/components/sourceresolve/api/src/main/java/org/apache/excalibur/source/SourceUtil.java?view=markup I think the best solution in this case is copying the encodeBASE64() method into the cocoon-pipeline module - it's just about 30 lines of code and it's rather unlikely that they have to be modified in the future. Support access to URLs that require authentication. --- Key: COCOON3-35 URL: https://issues.apache.org/jira/browse/COCOON3-35 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-sax, cocoon-stax, cocoon-stringtemplate Affects Versions: 3.0.0-alpha-1 Reporter: Steven Dolg Assignee: Cocoon Developers Team Priority: Minor Fix For: 3.0.0-alpha-2 Attachments: authentication.patch Currently our pipeline components cannot access URLs that require authentication. While it is possible to create specialized versions of each component and add authentication there, it shouldn't be too difficult to support this feature in every pipeline component we currently have. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (COCOON3-33) Cocoon-monitoring logging reconfiguration
[ https://issues.apache.org/jira/browse/COCOON3-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz reassigned COCOON3-33: - Assignee: Reinhard Poetz (was: Cocoon Developers Team) Cocoon-monitoring logging reconfiguration - Key: COCOON3-33 URL: https://issues.apache.org/jira/browse/COCOON3-33 Project: Cocoon 3 Issue Type: Task Components: cocoon-optional Reporter: Dariusz Łuksza Assignee: Reinhard Poetz Fix For: 3.0.0-alpha-2 Attachments: new-cocoon-monitoring-module.patch, new-cocoon-monitoring-module2.patch Setup new C3 module cocoon-monitoring and implement support for logging reconfiguration via JMX. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-33) Cocoon-monitoring logging reconfiguration
[ https://issues.apache.org/jira/browse/COCOON3-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-33. - Resolution: Fixed Fix Version/s: 3.0.0-alpha-2 Cocoon-monitoring logging reconfiguration - Key: COCOON3-33 URL: https://issues.apache.org/jira/browse/COCOON3-33 Project: Cocoon 3 Issue Type: Task Components: cocoon-optional Reporter: Dariusz Łuksza Assignee: Reinhard Poetz Fix For: 3.0.0-alpha-2 Attachments: new-cocoon-monitoring-module.patch, new-cocoon-monitoring-module2.patch Setup new C3 module cocoon-monitoring and implement support for logging reconfiguration via JMX. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-33) Cocoon-monitoring logging reconfiguration
[ https://issues.apache.org/jira/browse/COCOON3-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-33. - Resolution: Fixed I changed the dependency spring-jmx:2.0.8 to spring-context:2.5.6 - otherwise I applied the patch as it was. Cocoon-monitoring logging reconfiguration - Key: COCOON3-33 URL: https://issues.apache.org/jira/browse/COCOON3-33 Project: Cocoon 3 Issue Type: Task Components: cocoon-optional Reporter: Dariusz Łuksza Assignee: Reinhard Poetz Fix For: 3.0.0-alpha-2 Attachments: new-cocoon-monitoring-module.patch, new-cocoon-monitoring-module2.patch Setup new C3 module cocoon-monitoring and implement support for logging reconfiguration via JMX. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (COCOON3-33) Cocoon-monitoring logging reconfiguration
[ https://issues.apache.org/jira/browse/COCOON3-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz reopened COCOON3-33: --- Cocoon-monitoring logging reconfiguration - Key: COCOON3-33 URL: https://issues.apache.org/jira/browse/COCOON3-33 Project: Cocoon 3 Issue Type: Task Components: cocoon-optional Reporter: Dariusz Łuksza Assignee: Reinhard Poetz Fix For: 3.0.0-alpha-2 Attachments: new-cocoon-monitoring-module.patch, new-cocoon-monitoring-module2.patch Setup new C3 module cocoon-monitoring and implement support for logging reconfiguration via JMX. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON3-33) Cocoon-monitoring logging reconfiguration
[ https://issues.apache.org/jira/browse/COCOON3-33?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12704134#action_12704134 ] Reinhard Poetz commented on COCOON3-33: --- Unfortunatly I can't apply your patch. TortoiseSVN doesn't recognize it as one at all. After having a close look at I think that it is not a unified diff: diff --git a/cocoon-monitoring/pom.xml b/cocoon-monitoring/pom.xml new file mode 100644 index 000..f4b9f17 --- /dev/null +++ b/cocoon-monitoring/pom.xml @@ -0,0 +1,52 @@ +?xml version=1.0 encoding=UTF-8? Or did I something wrong? Cocoon-monitoring logging reconfiguration - Key: COCOON3-33 URL: https://issues.apache.org/jira/browse/COCOON3-33 Project: Cocoon 3 Issue Type: Task Components: cocoon-optional Reporter: Dariusz Łuksza Assignee: Cocoon Developers Team Attachments: new-cocoon-monitoring-module.patch Setup new C3 module cocoon-monitoring and implement support for logging reconfiguration via JMX. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Moved: (COCOON3-34) Attaching an aspect to org.apache.cocoon.sitemap.node.Sitemap leads to a ClassCastException
[ https://issues.apache.org/jira/browse/COCOON3-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz moved COCOON-2256 to COCOON3-34: --- Component/s: (was: - Components: Sitemap) cocoon-sitemap Affects Version/s: (was: 2.1.12-dev (Current SVN)) Key: COCOON3-34 (was: COCOON-2256) Project: Cocoon 3 (was: Cocoon) Attaching an aspect to org.apache.cocoon.sitemap.node.Sitemap leads to a ClassCastException - Key: COCOON3-34 URL: https://issues.apache.org/jira/browse/COCOON3-34 Project: Cocoon 3 Issue Type: Bug Components: cocoon-sitemap Reporter: Andreas Pinter Priority: Minor Attachments: cocoon.log I tried to attach an around-aspect for every node: @Around(execution(* invoke(..)) within(org.apache.cocoon.sitemap.node.*)) This led to a ClassCastException for the first sitemap. (see attached logfile) After excluding sitemap from my aspect, everything works just fine: @Around(execution(* invoke(..)) within(org.apache.cocoon.sitemap.node.* !org.apache.cocoon.sitemap.node.Sitemap)) Tested with cocoon-sample. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (COCOON3-34) Attaching an aspect to org.apache.cocoon.sitemap.node.Sitemap leads to a ClassCastException
[ https://issues.apache.org/jira/browse/COCOON3-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz reassigned COCOON3-34: - Assignee: Reinhard Poetz Attaching an aspect to org.apache.cocoon.sitemap.node.Sitemap leads to a ClassCastException - Key: COCOON3-34 URL: https://issues.apache.org/jira/browse/COCOON3-34 Project: Cocoon 3 Issue Type: Bug Components: cocoon-sitemap Reporter: Andreas Pinter Assignee: Reinhard Poetz Priority: Minor Attachments: cocoon.log I tried to attach an around-aspect for every node: @Around(execution(* invoke(..)) within(org.apache.cocoon.sitemap.node.*)) This led to a ClassCastException for the first sitemap. (see attached logfile) After excluding sitemap from my aspect, everything works just fine: @Around(execution(* invoke(..)) within(org.apache.cocoon.sitemap.node.* !org.apache.cocoon.sitemap.node.Sitemap)) Tested with cocoon-sample. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON3-34) Attaching an aspect to org.apache.cocoon.sitemap.node.Sitemap leads to a ClassCastException
[ https://issues.apache.org/jira/browse/COCOON3-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12703240#action_12703240 ] Reinhard Poetz commented on COCOON3-34: --- I've just applied (rev 769069) a patch to XMLSitemapServlet. Can you please check if this solves your problem? Thanks! Attaching an aspect to org.apache.cocoon.sitemap.node.Sitemap leads to a ClassCastException - Key: COCOON3-34 URL: https://issues.apache.org/jira/browse/COCOON3-34 Project: Cocoon 3 Issue Type: Bug Components: cocoon-sitemap Reporter: Andreas Pinter Assignee: Reinhard Poetz Priority: Minor Attachments: cocoon.log I tried to attach an around-aspect for every node: @Around(execution(* invoke(..)) within(org.apache.cocoon.sitemap.node.*)) This led to a ClassCastException for the first sitemap. (see attached logfile) After excluding sitemap from my aspect, everything works just fine: @Around(execution(* invoke(..)) within(org.apache.cocoon.sitemap.node.* !org.apache.cocoon.sitemap.node.Sitemap)) Tested with cocoon-sample. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON3-34) Attaching an aspect to org.apache.cocoon.sitemap.node.Sitemap leads to a ClassCastException
[ https://issues.apache.org/jira/browse/COCOON3-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12703330#action_12703330 ] Reinhard Poetz commented on COCOON3-34: --- I've applied another patch to get rid of (hopefully this time) all direct usages of Sitemap. Thanks for spotting Jörg! Attaching an aspect to org.apache.cocoon.sitemap.node.Sitemap leads to a ClassCastException - Key: COCOON3-34 URL: https://issues.apache.org/jira/browse/COCOON3-34 Project: Cocoon 3 Issue Type: Bug Components: cocoon-sitemap Reporter: Andreas Pinter Assignee: Reinhard Poetz Priority: Minor Attachments: cocoon.log I tried to attach an around-aspect for every node: @Around(execution(* invoke(..)) within(org.apache.cocoon.sitemap.node.*)) This led to a ClassCastException for the first sitemap. (see attached logfile) After excluding sitemap from my aspect, everything works just fine: @Around(execution(* invoke(..)) within(org.apache.cocoon.sitemap.node.* !org.apache.cocoon.sitemap.node.Sitemap)) Tested with cocoon-sample. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (COCOON3-32) Spring AOP doesn't work with REST controller beans
[ https://issues.apache.org/jira/browse/COCOON3-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz reassigned COCOON3-32: - Assignee: Reinhard Poetz (was: Cocoon Developers Team) Spring AOP doesn't work with REST controller beans -- Key: COCOON3-32 URL: https://issues.apache.org/jira/browse/COCOON3-32 Project: Cocoon 3 Issue Type: Bug Components: cocoon-rest Affects Versions: 3.0.0-alpha-1 Reporter: Reinhard Poetz Assignee: Reinhard Poetz Applying an advice on REST controller beans corrupts them because Spring AOP creates a proxy object that doesn't contain the original annotated fields anymore. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-32) Spring AOP doesn't work with REST controller beans
[ https://issues.apache.org/jira/browse/COCOON3-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-32. - Resolution: Fixed Fix Version/s: 3.0.0-alpha-2 Spring AOP doesn't work with REST controller beans -- Key: COCOON3-32 URL: https://issues.apache.org/jira/browse/COCOON3-32 Project: Cocoon 3 Issue Type: Bug Components: cocoon-rest Affects Versions: 3.0.0-alpha-1 Reporter: Reinhard Poetz Assignee: Reinhard Poetz Fix For: 3.0.0-alpha-2 Applying an advice on REST controller beans corrupts them because Spring AOP creates a proxy object that doesn't contain the original annotated fields anymore. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (COCOON3-32) Spring AOP doesn't work with REST controller beans
Spring AOP doesn't work with REST controller beans -- Key: COCOON3-32 URL: https://issues.apache.org/jira/browse/COCOON3-32 Project: Cocoon 3 Issue Type: Bug Components: cocoon-rest Affects Versions: 3.0.0-alpha-1 Reporter: Reinhard Poetz Assignee: Cocoon Developers Team Applying an advice on REST controller beans corrupts them because Spring AOP creates a proxy object that doesn't contain the original annotated fields anymore. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (COCOON3-28) [PATCH] documentation for stax-pipelines
[ https://issues.apache.org/jira/browse/COCOON3-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz reassigned COCOON3-28: - Assignee: Reinhard Poetz (was: Cocoon Developers Team) [PATCH] documentation for stax-pipelines Key: COCOON3-28 URL: https://issues.apache.org/jira/browse/COCOON3-28 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-docs, cocoon-stax Affects Versions: 3.0.0-alpha-2 Reporter: Andreas Pieber Assignee: Reinhard Poetz Fix For: 3.0.0-alpha-2 Attachments: stax-pipelines-docs.patch This patch should provide a first view on the documentation for the cocoon-stax components/pipeline. Most things are finished so far, and we think that this part could make its way into the code-base. Whats still not perfekt is the description of the transformers, but we're working on them. Nevertheless by releasing it we hope to get feedback and corrections ;) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (COCOON3-27) [PATCH] Add Java5 support
[ https://issues.apache.org/jira/browse/COCOON3-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz reassigned COCOON3-27: - Assignee: Reinhard Poetz (was: Cocoon Developers Team) [PATCH] Add Java5 support - Key: COCOON3-27 URL: https://issues.apache.org/jira/browse/COCOON3-27 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-stax Affects Versions: 3.0.0-alpha-2 Reporter: Andreas Pieber Assignee: Reinhard Poetz Fix For: 3.0.0-alpha-2 Attachments: stax-jdk1.5.patch Kilian pushed me at the fact that we could very easily support java5 in the StAX component. The only thing which have to be done for this is to add an optional dependency to the woodstox StAX implementation and remove all the @Override-Annotations from the code. So in a java6 environment the woodstox reference is not required and the module will work with the default implementation. For java5 the additional dependency is required. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-27) [PATCH] Add Java5 support
[ https://issues.apache.org/jira/browse/COCOON3-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-27. - Resolution: Fixed Patch applied - thanks Kilian and Andreas. [PATCH] Add Java5 support - Key: COCOON3-27 URL: https://issues.apache.org/jira/browse/COCOON3-27 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-stax Affects Versions: 3.0.0-alpha-2 Reporter: Andreas Pieber Assignee: Reinhard Poetz Fix For: 3.0.0-alpha-2 Attachments: stax-jdk1.5.patch Kilian pushed me at the fact that we could very easily support java5 in the StAX component. The only thing which have to be done for this is to add an optional dependency to the woodstox StAX implementation and remove all the @Override-Annotations from the code. So in a java6 environment the woodstox reference is not required and the module will work with the default implementation. For java5 the additional dependency is required. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON3-22) Remove XMLConsumer interface
[ https://issues.apache.org/jira/browse/COCOON3-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12674709#action_12674709 ] Reinhard Poetz commented on COCOON3-22: --- The patch doesn't cover the cocoon-stax module :-( Remove XMLConsumer interface Key: COCOON3-22 URL: https://issues.apache.org/jira/browse/COCOON3-22 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-sax Affects Versions: 3.0.0-alpha-1 Reporter: Carsten Ziegeler Assignee: Cocoon Developers Team Fix For: 3.0.0-alpha-2 Attachments: cocoon-3.patch, StAX-classes.png Remove XMLConsumer interface; relying on a content handler which might optionally implement lexical handler is sufficient and simplifies the module -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (COCOON3-22) Remove XMLConsumer interface
[ https://issues.apache.org/jira/browse/COCOON3-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12674709#action_12674709 ] reinh...@apache.org edited comment on COCOON3-22 at 2/18/09 9:39 AM: The patch doesn't cover the cocoon-stax module :-( BTW, there is it.bat (or it.sh of *nix) that runs all unit and integration tests and performs license header checks. was (Author: reinh...@apache.org): The patch doesn't cover the cocoon-stax module :-( Remove XMLConsumer interface Key: COCOON3-22 URL: https://issues.apache.org/jira/browse/COCOON3-22 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-sax Affects Versions: 3.0.0-alpha-1 Reporter: Carsten Ziegeler Assignee: Cocoon Developers Team Fix For: 3.0.0-alpha-2 Attachments: cocoon-3.patch, StAX-classes.png Remove XMLConsumer interface; relying on a content handler which might optionally implement lexical handler is sufficient and simplifies the module -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-17) Introduce the marker interface StAXPipelineComponent for the generified Pipeline interface.
[ https://issues.apache.org/jira/browse/COCOON3-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-17. - Resolution: Won't Fix Since this patch was part of COCOON3-17, it doesn't need to be applied. Introduce the marker interface StAXPipelineComponent for the generified Pipeline interface. --- Key: COCOON3-17 URL: https://issues.apache.org/jira/browse/COCOON3-17 Project: Cocoon 3 Issue Type: Bug Components: cocoon-stax Affects Versions: 3.0.0-alpha-1 Reporter: Steven Dolg Assignee: Steven Dolg Priority: Minor Fix For: 3.0.0-alpha-2 Attachments: stax-generics.patch Create the marker interface StaxPipelineComponent and have all PipelineComponents in the StAX module implement it. This will allow building type-safe pipelines for StAX components -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (COCOON3-20) [PATCH] stax stress tests
[ https://issues.apache.org/jira/browse/COCOON3-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz reassigned COCOON3-20: - Assignee: Reinhard Poetz (was: Cocoon Developers Team) [PATCH] stax stress tests - Key: COCOON3-20 URL: https://issues.apache.org/jira/browse/COCOON3-20 Project: Cocoon 3 Issue Type: Sub-task Components: cocoon-stax Reporter: Andreas Pieber Assignee: Reinhard Poetz Attachments: cocooon-stax-stress.patch The cocoon-stax-stress patch contains stress tests for cocoon stax. These are required since the cocoon-stax implementation relys on buffers and it should be checked if no overflows or memory leaks occur. Since the tests require some minutes to run they're inacceptable for regression testing during development. Therefore they should be configured to run in the integration test phase. I created this issue as an subtask of COCOON3-18 since first the patch of COCOON3-18 have to be applied before this patch could be used. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-20) [PATCH] stax stress tests
[ https://issues.apache.org/jira/browse/COCOON3-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-20. - Resolution: Fixed Fix Version/s: 3.0.0-alpha-2 patch applied. The tests are only executed with Maven if the 'stress' profile is activated. [PATCH] stax stress tests - Key: COCOON3-20 URL: https://issues.apache.org/jira/browse/COCOON3-20 Project: Cocoon 3 Issue Type: Sub-task Components: cocoon-stax Reporter: Andreas Pieber Assignee: Reinhard Poetz Fix For: 3.0.0-alpha-2 Attachments: cocooon-stax-stress.patch The cocoon-stax-stress patch contains stress tests for cocoon stax. These are required since the cocoon-stax implementation relys on buffers and it should be checked if no overflows or memory leaks occur. Since the tests require some minutes to run they're inacceptable for regression testing during development. Therefore they should be configured to run in the integration test phase. I created this issue as an subtask of COCOON3-18 since first the patch of COCOON3-18 have to be applied before this patch could be used. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON3-19) [PATCH] stax-sax converter
[ https://issues.apache.org/jira/browse/COCOON3-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12671466#action_12671466 ] Reinhard Poetz commented on COCOON3-19: --- I've just committed the license patch. Thanks! [PATCH] stax-sax converter -- Key: COCOON3-19 URL: https://issues.apache.org/jira/browse/COCOON3-19 Project: Cocoon 3 Issue Type: Sub-task Components: cocoon-stax Reporter: Andreas Pieber Assignee: Reinhard Poetz Attachments: cocoon-stax-license.patch, cocooon-stax-converter.patch We experimented with wrappers to add SAX-components to StAX pipelines and with Adapters between StAX pipelines and SAX pipelines. IMO they work quite fine :) The problem with this patch is that it relies on the stax-utils project. Most classes in o.a.c.stax.converter.util are redistrubuted from the stax-utils (https://stax-utils.dev.java.net/) project. This was required since there's an architectural issue so that stax-utils can not be used directly as reference. I posted at the stax-utils dev mailing list two weeks ago, if they could make some of their methods protected instead of private so that we could resolve this issue, but I did not receive an answer. I created a seperated issue for this problem since there's the opened question of how to mark the redistributed classes from the stax-utils project. I think Reinhard know ways of how to resolve this problem :) I created this issue as an subtask of COCOON3-18 since first the patch of COCOON3-18 have to be applied before this patch could be used. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COCOON3-3) Provide an XInclude transformer as a PipelineComponent
[ https://issues.apache.org/jira/browse/COCOON3-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz updated COCOON3-3: - Component/s: (was: cocoon-pipeline) cocoon-sax Provide an XInclude transformer as a PipelineComponent -- Key: COCOON3-3 URL: https://issues.apache.org/jira/browse/COCOON3-3 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-sax Affects Versions: 3.0.0-alpha-2 Reporter: Simone Tripodi Assignee: Cocoon Developers Team Priority: Minor Fix For: 3.0.0-alpha-2 Attachments: XInclude.patch, XIncludeTransformerFixedAndApacheHeaders.patch Oldest versions of cocoon already contain an XInclude transformer, it could be a good starting point: http://svn.eu.apache.org/repos/asf/cocoon/trunk/core/cocoon-pipeline/cocoon-pipeline-components/src/main/java/org/apache/cocoon/transformation/XIncludeTransformer.java XPointer package's dependencies should be reduced to be imported in the new pipeline: http://svn.eu.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/src/java/org/apache/cocoon/components/xpointer An alternative solution could be using xerces2 APIs: http://xerces.apache.org/xerces2-j/faq-xinclude.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-10) Packages could be re-organized
[ https://issues.apache.org/jira/browse/COCOON3-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-10. - Resolution: Fixed All SAX specific classes were moved into a separate module. While doing this the package structure was also restructured. Packages could be re-organized -- Key: COCOON3-10 URL: https://issues.apache.org/jira/browse/COCOON3-10 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-pipeline Affects Versions: 3.0.0-alpha-2 Reporter: Simone Tripodi Assignee: Cocoon Developers Team Priority: Trivial Fix For: 3.0.0-alpha-2 Attachments: PackageOrganizing.patch According to older cocoon's taxonomy, packages - particularly the xml package - could be re-organized, discerning the roles of cocoon's components: - generators - serializers - transformer This is a nice way to maintain well-organized the code. What do you think about it? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-14) Use generics for pipeline assembly
[ https://issues.apache.org/jira/browse/COCOON3-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-14. - Resolution: Fixed Fix Version/s: 3.0.0-alpha-2 Patch was already applied. Use generics for pipeline assembly -- Key: COCOON3-14 URL: https://issues.apache.org/jira/browse/COCOON3-14 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-pipeline Reporter: Carsten Ziegeler Assignee: Cocoon Developers Team Fix For: 3.0.0-alpha-2 Attachments: generics.patch This is a simple patch to add generics to the pipeline interface and impl. With additionally introducing marker interfaces for the component types (SAX, Stax, dom) this would allow compile time checks if all components have the correct type when assembling the pipeline. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-12) StAX research
[ https://issues.apache.org/jira/browse/COCOON3-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-12. - Resolution: Fixed Fix Version/s: 3.0.0-alpha-2 This patch was created to keep a copy of the research document but there is no further action required. StAX research - Key: COCOON3-12 URL: https://issues.apache.org/jira/browse/COCOON3-12 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-pipeline Reporter: Thorsten Scherler Assignee: Cocoon Developers Team Priority: Trivial Fix For: 3.0.0-alpha-2 Attachments: Stax_Analysis.pdf http://marc.info/?t=12301125342r=1w=2 An evaluation of the latest XML processing technologies regarding their usability in Cocoon3 (especially if there are suited to be used in a streaming pipeline). As it's commonly know we decided to use StAX as our weapon of choice to do the XML, but this paper should explain the whys and hows and especially the way we took to come to our decision, which resulted in using the very same API. Eleven pages should be a to big read and it contains all necessary links to all the APIs we evaluated and also line wise our two cents about the API we observed. Concludingly we also tried to show the difference between the currently used SAX and the of us proposed StAX API. I hope this work sheds some light on our decision making and taking and that someone dares to read it. posted by Michael Seydl -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-18) [PATCH] cocoon-stax core
[ https://issues.apache.org/jira/browse/COCOON3-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-18. - Resolution: Fixed Fix Version/s: 3.0.0-alpha-2 All patches are committed. [PATCH] cocoon-stax core Key: COCOON3-18 URL: https://issues.apache.org/jira/browse/COCOON3-18 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-stax Reporter: Andreas Pieber Assignee: Reinhard Poetz Fix For: 3.0.0-alpha-2 Attachments: cocooon-stax-core.patch Since our last release some time passed by and we did many changes to the core of the cocoon-stax module. The changes contained by this patch could be summerized as: * Introduced the marker interface for StAXPipelineComponent for the generified Pipeline interface as proposed by steven in COCOON3-17. * Introduced a general workflow for working the peek() and nextEvent() calls in the same way * Increased the documentation at many places in the code * Introduced regex attribute finding capabilities to the FindStartElementNavigator and the InSubtreeNavigator * Added some additional testcases which also could be used as examples. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COCOON3-19) [PATCH] stax-sax converter
[ https://issues.apache.org/jira/browse/COCOON3-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz updated COCOON3-19: -- Fix Version/s: 3.0.0-alpha-2 [PATCH] stax-sax converter -- Key: COCOON3-19 URL: https://issues.apache.org/jira/browse/COCOON3-19 Project: Cocoon 3 Issue Type: Sub-task Components: cocoon-stax Reporter: Andreas Pieber Assignee: Reinhard Poetz Fix For: 3.0.0-alpha-2 Attachments: cocoon-stax-license.patch, cocooon-stax-converter.patch We experimented with wrappers to add SAX-components to StAX pipelines and with Adapters between StAX pipelines and SAX pipelines. IMO they work quite fine :) The problem with this patch is that it relies on the stax-utils project. Most classes in o.a.c.stax.converter.util are redistrubuted from the stax-utils (https://stax-utils.dev.java.net/) project. This was required since there's an architectural issue so that stax-utils can not be used directly as reference. I posted at the stax-utils dev mailing list two weeks ago, if they could make some of their methods protected instead of private so that we could resolve this issue, but I did not receive an answer. I created a seperated issue for this problem since there's the opened question of how to mark the redistributed classes from the stax-utils project. I think Reinhard know ways of how to resolve this problem :) I created this issue as an subtask of COCOON3-18 since first the patch of COCOON3-18 have to be applied before this patch could be used. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (COCOON3-26) Integrate the cocoon subproject 'cocoon-xml'
Integrate the cocoon subproject 'cocoon-xml' Key: COCOON3-26 URL: https://issues.apache.org/jira/browse/COCOON3-26 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-sax Reporter: Reinhard Poetz Assignee: Cocoon Developers Team Fix For: 3.0.0-alpha-2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COCOON3-26) Integrate the cocoon subproject 'cocoon-xml'
[ https://issues.apache.org/jira/browse/COCOON3-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz updated COCOON3-26: -- Attachment: cocoon-xml.patch The patch Integrate the cocoon subproject 'cocoon-xml' Key: COCOON3-26 URL: https://issues.apache.org/jira/browse/COCOON3-26 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-sax Reporter: Reinhard Poetz Assignee: Cocoon Developers Team Fix For: 3.0.0-alpha-2 Attachments: cocoon-xml.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (COCOON3-18) [PATCH] cocoon-stax core
[ https://issues.apache.org/jira/browse/COCOON3-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz reassigned COCOON3-18: - Assignee: Reinhard Poetz (was: Cocoon Developers Team) [PATCH] cocoon-stax core Key: COCOON3-18 URL: https://issues.apache.org/jira/browse/COCOON3-18 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-stax Reporter: Andreas Pieber Assignee: Reinhard Poetz Attachments: cocooon-stax-core.patch Since our last release some time passed by and we did many changes to the core of the cocoon-stax module. The changes contained by this patch could be summerized as: * Introduced the marker interface for StAXPipelineComponent for the generified Pipeline interface as proposed by steven in COCOON3-17. * Introduced a general workflow for working the peek() and nextEvent() calls in the same way * Increased the documentation at many places in the code * Introduced regex attribute finding capabilities to the FindStartElementNavigator and the InSubtreeNavigator * Added some additional testcases which also could be used as examples. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON3-19) [PATCH] stax-sax converter
[ https://issues.apache.org/jira/browse/COCOON3-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12670153#action_12670153 ] Reinhard Poetz commented on COCOON3-19: --- According to http://www.apache.org/legal/src-headers.html#3party we should not modify or remove any copyright notices or licenses within third-party works. This means we have to keep the original license header (According to https://stax-utils.dev.java.net/ Stax-Utils has a BSD style license) and have to include a reference in the NOTICE file. Andreas (or anybody else), could you please list all the files that are taken from StAXUtils and point me to the original license? Thanks! [PATCH] stax-sax converter -- Key: COCOON3-19 URL: https://issues.apache.org/jira/browse/COCOON3-19 Project: Cocoon 3 Issue Type: Sub-task Components: cocoon-stax Reporter: Andreas Pieber Assignee: Cocoon Developers Team Attachments: cocooon-stax-converter.patch We experimented with wrappers to add SAX-components to StAX pipelines and with Adapters between StAX pipelines and SAX pipelines. IMO they work quite fine :) The problem with this patch is that it relies on the stax-utils project. Most classes in o.a.c.stax.converter.util are redistrubuted from the stax-utils (https://stax-utils.dev.java.net/) project. This was required since there's an architectural issue so that stax-utils can not be used directly as reference. I posted at the stax-utils dev mailing list two weeks ago, if they could make some of their methods protected instead of private so that we could resolve this issue, but I did not receive an answer. I created a seperated issue for this problem since there's the opened question of how to mark the redistributed classes from the stax-utils project. I think Reinhard know ways of how to resolve this problem :) I created this issue as an subtask of COCOON3-18 since first the patch of COCOON3-18 have to be applied before this patch could be used. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (COCOON3-19) [PATCH] stax-sax converter
[ https://issues.apache.org/jira/browse/COCOON3-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12670131#action_12670131 ] reinh...@apache.org edited comment on COCOON3-19 at 2/3/09 2:45 PM: --- Andreas, can you give us a pointer to your message sent to the stax-utils community? (Just for the records) was (Author: reinh...@apache.org): Andreas, can you give a pointer to your message sent to the stax-utils community? [PATCH] stax-sax converter -- Key: COCOON3-19 URL: https://issues.apache.org/jira/browse/COCOON3-19 Project: Cocoon 3 Issue Type: Sub-task Components: cocoon-stax Reporter: Andreas Pieber Assignee: Cocoon Developers Team Attachments: cocooon-stax-converter.patch We experimented with wrappers to add SAX-components to StAX pipelines and with Adapters between StAX pipelines and SAX pipelines. IMO they work quite fine :) The problem with this patch is that it relies on the stax-utils project. Most classes in o.a.c.stax.converter.util are redistrubuted from the stax-utils (https://stax-utils.dev.java.net/) project. This was required since there's an architectural issue so that stax-utils can not be used directly as reference. I posted at the stax-utils dev mailing list two weeks ago, if they could make some of their methods protected instead of private so that we could resolve this issue, but I did not receive an answer. I created a seperated issue for this problem since there's the opened question of how to mark the redistributed classes from the stax-utils project. I think Reinhard know ways of how to resolve this problem :) I created this issue as an subtask of COCOON3-18 since first the patch of COCOON3-18 have to be applied before this patch could be used. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON3-19) [PATCH] stax-sax converter
[ https://issues.apache.org/jira/browse/COCOON3-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12670131#action_12670131 ] Reinhard Poetz commented on COCOON3-19: --- Andreas, can you give a pointer to your message sent to the stax-utils community? [PATCH] stax-sax converter -- Key: COCOON3-19 URL: https://issues.apache.org/jira/browse/COCOON3-19 Project: Cocoon 3 Issue Type: Sub-task Components: cocoon-stax Reporter: Andreas Pieber Assignee: Cocoon Developers Team Attachments: cocooon-stax-converter.patch We experimented with wrappers to add SAX-components to StAX pipelines and with Adapters between StAX pipelines and SAX pipelines. IMO they work quite fine :) The problem with this patch is that it relies on the stax-utils project. Most classes in o.a.c.stax.converter.util are redistrubuted from the stax-utils (https://stax-utils.dev.java.net/) project. This was required since there's an architectural issue so that stax-utils can not be used directly as reference. I posted at the stax-utils dev mailing list two weeks ago, if they could make some of their methods protected instead of private so that we could resolve this issue, but I did not receive an answer. I created a seperated issue for this problem since there's the opened question of how to mark the redistributed classes from the stax-utils project. I think Reinhard know ways of how to resolve this problem :) I created this issue as an subtask of COCOON3-18 since first the patch of COCOON3-18 have to be applied before this patch could be used. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (COCOON3-19) [PATCH] stax-sax converter
[ https://issues.apache.org/jira/browse/COCOON3-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz reassigned COCOON3-19: - Assignee: Reinhard Poetz (was: Cocoon Developers Team) [PATCH] stax-sax converter -- Key: COCOON3-19 URL: https://issues.apache.org/jira/browse/COCOON3-19 Project: Cocoon 3 Issue Type: Sub-task Components: cocoon-stax Reporter: Andreas Pieber Assignee: Reinhard Poetz Attachments: cocooon-stax-converter.patch We experimented with wrappers to add SAX-components to StAX pipelines and with Adapters between StAX pipelines and SAX pipelines. IMO they work quite fine :) The problem with this patch is that it relies on the stax-utils project. Most classes in o.a.c.stax.converter.util are redistrubuted from the stax-utils (https://stax-utils.dev.java.net/) project. This was required since there's an architectural issue so that stax-utils can not be used directly as reference. I posted at the stax-utils dev mailing list two weeks ago, if they could make some of their methods protected instead of private so that we could resolve this issue, but I did not receive an answer. I created a seperated issue for this problem since there's the opened question of how to mark the redistributed classes from the stax-utils project. I think Reinhard know ways of how to resolve this problem :) I created this issue as an subtask of COCOON3-18 since first the patch of COCOON3-18 have to be applied before this patch could be used. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON3-19) [PATCH] stax-sax converter
[ https://issues.apache.org/jira/browse/COCOON3-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12670208#action_12670208 ] Reinhard Poetz commented on COCOON3-19: --- I've applied the patch but keep the issue open until the Cocoon PMC has confirmed that I did the licensing part correctly. [PATCH] stax-sax converter -- Key: COCOON3-19 URL: https://issues.apache.org/jira/browse/COCOON3-19 Project: Cocoon 3 Issue Type: Sub-task Components: cocoon-stax Reporter: Andreas Pieber Assignee: Reinhard Poetz Attachments: cocooon-stax-converter.patch We experimented with wrappers to add SAX-components to StAX pipelines and with Adapters between StAX pipelines and SAX pipelines. IMO they work quite fine :) The problem with this patch is that it relies on the stax-utils project. Most classes in o.a.c.stax.converter.util are redistrubuted from the stax-utils (https://stax-utils.dev.java.net/) project. This was required since there's an architectural issue so that stax-utils can not be used directly as reference. I posted at the stax-utils dev mailing list two weeks ago, if they could make some of their methods protected instead of private so that we could resolve this issue, but I did not receive an answer. I created a seperated issue for this problem since there's the opened question of how to mark the redistributed classes from the stax-utils project. I think Reinhard know ways of how to resolve this problem :) I created this issue as an subtask of COCOON3-18 since first the patch of COCOON3-18 have to be applied before this patch could be used. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON3-19) [PATCH] stax-sax converter
[ https://issues.apache.org/jira/browse/COCOON3-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12670260#action_12670260 ] Reinhard Poetz commented on COCOON3-19: --- Yes, getting a patch with the original license headers would be great. We don't want to keep the SVN because they will be overridden anyway. Could you also please add a comment of the revision number or release version that those files are taken from? [PATCH] stax-sax converter -- Key: COCOON3-19 URL: https://issues.apache.org/jira/browse/COCOON3-19 Project: Cocoon 3 Issue Type: Sub-task Components: cocoon-stax Reporter: Andreas Pieber Assignee: Reinhard Poetz Attachments: cocooon-stax-converter.patch We experimented with wrappers to add SAX-components to StAX pipelines and with Adapters between StAX pipelines and SAX pipelines. IMO they work quite fine :) The problem with this patch is that it relies on the stax-utils project. Most classes in o.a.c.stax.converter.util are redistrubuted from the stax-utils (https://stax-utils.dev.java.net/) project. This was required since there's an architectural issue so that stax-utils can not be used directly as reference. I posted at the stax-utils dev mailing list two weeks ago, if they could make some of their methods protected instead of private so that we could resolve this issue, but I did not receive an answer. I created a seperated issue for this problem since there's the opened question of how to mark the redistributed classes from the stax-utils project. I think Reinhard know ways of how to resolve this problem :) I created this issue as an subtask of COCOON3-18 since first the patch of COCOON3-18 have to be applied before this patch could be used. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-21) mac/linux bat-incompatibility
[ https://issues.apache.org/jira/browse/COCOON3-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-21. - Resolution: Fixed I've applied it.sh but not svn-release-tags.sh. If somebody wants to use it on mac/linux its better to copy it manually than IMO. Thanks Andreas! mac/linux bat-incompatibility - Key: COCOON3-21 URL: https://issues.apache.org/jira/browse/COCOON3-21 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-docs Affects Versions: 3.0.0-alpha-1 Reporter: Andreas Pieber Assignee: Reinhard Poetz Fix For: 3.0.0-alpha-2 Attachments: linux-mac-exec.patch Since the REM tag is not know by linux/mac bash at this platforms all commands in the it.bat and svn-release-tags.bat have to be executed by hand. Possible solution: bash executable doing the same as the .bat files Drawback: two files to maintain with (more or less) the identical content. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (COCOON3-25) AbstractXMLPipe does the same as XMLConsumerAdapter.
AbstractXMLPipe does the same as XMLConsumerAdapter. Key: COCOON3-25 URL: https://issues.apache.org/jira/browse/COCOON3-25 Project: Cocoon 3 Issue Type: Bug Components: cocoon-sax Affects Versions: 3.0.0-alpha-1 Reporter: Reinhard Poetz Assignee: Reinhard Poetz Fix For: 3.0.0-alpha-2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-25) AbstractXMLPipe does the same as XMLConsumerAdapter.
[ https://issues.apache.org/jira/browse/COCOON3-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-25. - Resolution: Fixed AbstractXMLPipe does the same as XMLConsumerAdapter. Key: COCOON3-25 URL: https://issues.apache.org/jira/browse/COCOON3-25 Project: Cocoon 3 Issue Type: Bug Components: cocoon-sax Affects Versions: 3.0.0-alpha-1 Reporter: Reinhard Poetz Assignee: Reinhard Poetz Fix For: 3.0.0-alpha-2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-24) Cleanup PipelineComponent#finish()
[ https://issues.apache.org/jira/browse/COCOON3-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-24. - Resolution: Fixed Cleanup PipelineComponent#finish() -- Key: COCOON3-24 URL: https://issues.apache.org/jira/browse/COCOON3-24 Project: Cocoon 3 Issue Type: Bug Components: cocoon-pipeline Reporter: Reinhard Poetz Assignee: Reinhard Poetz Fix For: 3.0.0-alpha-2 Remove the exception parameter from the PipelineComponent#finish() method. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON3-14) Use generics for pipeline assembly
[ https://issues.apache.org/jira/browse/COCOON3-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12666922#action_12666922 ] Reinhard Poetz commented on COCOON3-14: --- I think this patch will be the best solution that the Java programming language can support. Grek, your ideas are interesting but I fail to see how this could ever work with Java. So here's my +1 for Carsten's patch. @Grek: We won't reach beta before Amsterdam, which means that we can still change core contracts. Use generics for pipeline assembly -- Key: COCOON3-14 URL: https://issues.apache.org/jira/browse/COCOON3-14 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-pipeline Reporter: Carsten Ziegeler Assignee: Cocoon Developers Team Attachments: generics.patch This is a simple patch to add generics to the pipeline interface and impl. With additionally introducing marker interfaces for the component types (SAX, Stax, dom) this would allow compile time checks if all components have the correct type when assembling the pipeline. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-11) [PATCH] Initial patch for the cocoon-stax pipeline implementation
[ https://issues.apache.org/jira/browse/COCOON3-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-11. - Resolution: Fixed I've applied your patch with some minor modifications (see the commit message) [PATCH] Initial patch for the cocoon-stax pipeline implementation - Key: COCOON3-11 URL: https://issues.apache.org/jira/browse/COCOON3-11 Project: Cocoon 3 Issue Type: New Feature Components: cocoon-pipeline Reporter: Michael Seydl Assignee: Reinhard Poetz Fix For: 3.0.0-alpha-2 Attachments: cocoon-stax.patch This patch represents the first attempt to implement a stax pipeline. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-5) Add an HTML2XHTML converter as Starter
[ https://issues.apache.org/jira/browse/COCOON3-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-5. Resolution: Fixed Thanks Simone! We applied your patch with some minor modification so that it runs with sitemaps too. Add an HTML2XHTML converter as Starter -- Key: COCOON3-5 URL: https://issues.apache.org/jira/browse/COCOON3-5 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-optional Affects Versions: 3.0.0-alpha-2 Reporter: Simone Tripodi Assignee: Cocoon Developers Team Priority: Minor Fix For: 3.0.0-alpha-2 Attachments: NekoGenerator.patch This starter component for the pipeline is a component that transform an HTML content, taken by the specified URL, and transform it in XHTML or, at least, a well-formed XML document. So now the original document can be processed in the pipeline in various ways: * following links; * implementing crwalers; * easy transforming the original document in other various formats; * etc... I want to explain the need of this component with a testcase; last week I had to face a singular problem, realizing a simple service that takes in input an HTML page's URL, and transform it , through the Optimus' XSLT (http://microformatique.com/optimus - http://code.google.com/p/mf-optimus/source/browse/#svn/trunk/xsl) in an XML document that contains the original doc's Microformats, in an easier and more parsable formats. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (COCOON3-2) Add an XSchema Validator as PipelineComponent
[ https://issues.apache.org/jira/browse/COCOON3-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reinhard Poetz closed COCOON3-2. Resolution: Fixed Patch applied. Thanks Simone! Add an XSchema Validator as PipelineComponent - Key: COCOON3-2 URL: https://issues.apache.org/jira/browse/COCOON3-2 Project: Cocoon 3 Issue Type: Improvement Components: cocoon-pipeline Affects Versions: 3.0.0-alpha-2 Reporter: Simone Tripodi Assignee: Reinhard Poetz Priority: Minor Fix For: 3.0.0-alpha-2 Attachments: SchemaProcessorInSiteMap.patch, XSchemaProcessor.patch XSchema Validation can be performed as an Identity Transformer where the input will be filter by the XSchema validation. An error occurs - and the pipeline will be break - when the input is not valid against the declared XML Schema. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
