[jira] [Updated] (COCOON-2372) Release Cocoon 2.2.1

2022-12-18 Thread Javier Puerto (Jira)


 [ 
https://issues.apache.org/jira/browse/COCOON-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javier Puerto updated COCOON-2372:
--
Status: Continued  (was: Blocked)

> Release Cocoon 2.2.1
> 
>
> Key: COCOON-2372
> URL: https://issues.apache.org/jira/browse/COCOON-2372
> Project: Cocoon
>  Issue Type: Task
>  Components: * Cocoon Core, Blocks: Captcha, Blocks: Databases, 
> Blocks: ImageOp, Blocks: XSP
>Affects Versions: 2.2
>Reporter: Javier Puerto
>Priority: Major
> Fix For: 2.2.1
>
>
> Maintenance release for Java 8 compatibility improvements.
> * Deprecate ImageOP and Capcha blocks because it depends on obsolete Java 
> image API.
> * Update DataSource implementations (only wrappers) to implement the method 
> [https://docs.oracle.com/javase/7/docs/api/javax/sql/CommonDataSource.html#getParentLogger()]
>  introduced in Java 1.7.
> * Update XSP block with newer Eclipe JDK compiler to support Java 8.
> Furthermore, the following issues will be addressed:
> * Fix test cases for JCR block by excluding a SLF4J dependency that was not 
> working with our current Spring version.
> * Other bugfixes.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (COCOON-2372) Release Cocoon 2.2.1

2022-12-18 Thread Javier Puerto (Jira)


 [ 
https://issues.apache.org/jira/browse/COCOON-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javier Puerto updated COCOON-2372:
--
Status: Blocked  (was: Open)

> Release Cocoon 2.2.1
> 
>
> Key: COCOON-2372
> URL: https://issues.apache.org/jira/browse/COCOON-2372
> Project: Cocoon
>  Issue Type: Task
>  Components: * Cocoon Core, Blocks: Captcha, Blocks: Databases, 
> Blocks: ImageOp, Blocks: XSP
>Affects Versions: 2.2
>Reporter: Javier Puerto
>Priority: Major
> Fix For: 2.2.1
>
>
> Maintenance release for Java 8 compatibility improvements.
> * Deprecate ImageOP and Capcha blocks because it depends on obsolete Java 
> image API.
> * Update DataSource implementations (only wrappers) to implement the method 
> [https://docs.oracle.com/javase/7/docs/api/javax/sql/CommonDataSource.html#getParentLogger()]
>  introduced in Java 1.7.
> * Update XSP block with newer Eclipe JDK compiler to support Java 8.
> Furthermore, the following issues will be addressed:
> * Fix test cases for JCR block by excluding a SLF4J dependency that was not 
> working with our current Spring version.
> * Other bugfixes.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (COCOON-2372) Release Cocoon 2.2.1

2022-12-18 Thread Javier Puerto (Jira)


 [ 
https://issues.apache.org/jira/browse/COCOON-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javier Puerto updated COCOON-2372:
--
Description: 
Maintenance release for Java 8 compatibility improvements.

* Deprecate ImageOP and Capcha blocks because it depends on obsolete Java image 
API.
* Update DataSource implementations (only wrappers) to implement the method 
[https://docs.oracle.com/javase/7/docs/api/javax/sql/CommonDataSource.html#getParentLogger()]
 introduced in Java 1.7.
* Update XSP block with newer Eclipe JDK compiler to support Java 8.

Furthermore, the following issues will be addressed:

* Fix test cases for JCR block by excluding a SLF4J dependency that was not 
working with our current Spring version.
* Other bugfixes.



  was:
Maintenance release for Java 8 compatibility improvements.

* Deprecate ImageOP and Capcha blocks because it depends on obsolete Java image 
API.
* Update DataSource implementations (only wrappers) to implement the method 
[https://docs.oracle.com/javase/7/docs/api/javax/sql/CommonDataSource.html#getParentLogger()]
 introduced in Java 1.7.
* Update XSP block with newer Eclipe JDK compiler to support Java 8.

Furthermore, the following issues will be addressed:

* Fix test cases for JCR block by excluding a SLF4J dependency that was not 
working with our current Spring version.
* Other bugfixes.
* Exclude conflicting dependency from JCR block incompatible with o




> Release Cocoon 2.2.1
> 
>
> Key: COCOON-2372
> URL: https://issues.apache.org/jira/browse/COCOON-2372
> Project: Cocoon
>  Issue Type: Task
>  Components: * Cocoon Core, Blocks: Captcha, Blocks: Databases, 
> Blocks: ImageOp, Blocks: XSP
>Affects Versions: 2.2
>Reporter: Javier Puerto
>Priority: Major
> Fix For: 2.2.1
>
>
> Maintenance release for Java 8 compatibility improvements.
> * Deprecate ImageOP and Capcha blocks because it depends on obsolete Java 
> image API.
> * Update DataSource implementations (only wrappers) to implement the method 
> [https://docs.oracle.com/javase/7/docs/api/javax/sql/CommonDataSource.html#getParentLogger()]
>  introduced in Java 1.7.
> * Update XSP block with newer Eclipe JDK compiler to support Java 8.
> Furthermore, the following issues will be addressed:
> * Fix test cases for JCR block by excluding a SLF4J dependency that was not 
> working with our current Spring version.
> * Other bugfixes.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (COCOON-2372) Release Cocoon 2.2.1

2022-12-18 Thread Javier Puerto (Jira)


 [ 
https://issues.apache.org/jira/browse/COCOON-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javier Puerto updated COCOON-2372:
--
Description: 
Maintenance release for Java 8 compatibility improvements.

* Deprecate ImageOP and Capcha blocks because it depends on obsolete Java image 
API.
* Update DataSource implementations (only wrappers) to implement the method 
[https://docs.oracle.com/javase/7/docs/api/javax/sql/CommonDataSource.html#getParentLogger()]
 introduced in Java 1.7.
* Update XSP block with newer Eclipe JDK compiler to support Java 8.

Furthermore, the following issues will be addressed:

* Fix test cases for JCR block by excluding a SLF4J dependency that was not 
working with our current Spring version.
* Other bugfixes.
* Exclude conflicting dependency from JCR block incompatible with o



  was:
Maintenance release for Java 8 compatibility improvements.

* Deprecate ImageOP and Capcha blocks because it depends on obsolete Java image 
API.
* Update DataSource implementations (only wrappers) to implement the method 
[getParentLogger()|https://docs.oracle.com/javase/7/docs/api/javax/sql/CommonDataSource.html#getParentLogger()]
 introduced in Java 1.7.
* Update XSP block with newer Eclipe JDK compiler to support Java 8.

Furthermore, the following issues will be addressed:

* Fix test cases for JCR block by excluding a SLF4J dependency that was not 
working with our current Spring version.
* Other bugfixes.
* Exclude conflicting dependency from JCR block incompatible with o




> Release Cocoon 2.2.1
> 
>
> Key: COCOON-2372
> URL: https://issues.apache.org/jira/browse/COCOON-2372
> Project: Cocoon
>  Issue Type: Task
>  Components: * Cocoon Core, Blocks: Captcha, Blocks: Databases, 
> Blocks: ImageOp, Blocks: XSP
>Affects Versions: 2.2
>Reporter: Javier Puerto
>Priority: Major
> Fix For: 2.2.1
>
>
> Maintenance release for Java 8 compatibility improvements.
> * Deprecate ImageOP and Capcha blocks because it depends on obsolete Java 
> image API.
> * Update DataSource implementations (only wrappers) to implement the method 
> [https://docs.oracle.com/javase/7/docs/api/javax/sql/CommonDataSource.html#getParentLogger()]
>  introduced in Java 1.7.
> * Update XSP block with newer Eclipe JDK compiler to support Java 8.
> Furthermore, the following issues will be addressed:
> * Fix test cases for JCR block by excluding a SLF4J dependency that was not 
> working with our current Spring version.
> * Other bugfixes.
> * Exclude conflicting dependency from JCR block incompatible with o



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (COCOON-2372) Release Cocoon 2.2.1

2022-12-18 Thread Javier Puerto (Jira)
Javier Puerto created COCOON-2372:
-

 Summary: Release Cocoon 2.2.1
 Key: COCOON-2372
 URL: https://issues.apache.org/jira/browse/COCOON-2372
 Project: Cocoon
  Issue Type: Task
  Components: * Cocoon Core, Blocks: Captcha, Blocks: Databases, 
Blocks: ImageOp, Blocks: XSP
Affects Versions: 2.2
Reporter: Javier Puerto
 Fix For: 2.2.1


Maintenance release for Java 8 compatibility improvements.

* Deprecate ImageOP and Capcha blocks because it depends on obsolete Java image 
API.
* Update DataSource implementations (only wrappers) to implement the method 
[getParentLogger()|https://docs.oracle.com/javase/7/docs/api/javax/sql/CommonDataSource.html#getParentLogger()]
 introduced in Java 1.7.
* Update XSP block with newer Eclipe JDK compiler to support Java 8.

Furthermore, the following issues will be addressed:

* Fix test cases for JCR block by excluding a SLF4J dependency that was not 
working with our current Spring version.
* Other bugfixes.
* Exclude conflicting dependency from JCR block incompatible with o





--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Assigned] (COCOON-2347) Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version

2015-10-31 Thread Javier Puerto (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javier Puerto reassigned COCOON-2347:
-

Assignee: Javier Puerto

> Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version
> -
>
> Key: COCOON-2347
> URL: https://issues.apache.org/jira/browse/COCOON-2347
> Project: Cocoon
>  Issue Type: Improvement
>  Components: * Cocoon Core, - Components: Sitemap, - Expression 
> language, - Servlet service framework
>Affects Versions: 2.2
>Reporter: Gabriel Gruber
>Assignee: Javier Puerto
> Attachments: AbstractElementParser.java.patch, 
> AbstractTestCase.java.patch, BeanMapElementParser.java.patch, 
> BridgeElementParser.java.patch, CallScope.java.patch, 
> MockRequestAttributes.java.patch, MultiMap.java, MultiValueMap.java, 
> ObjectModel.java.patch, ObjectModelImpl.java.patch, 
> PipelineComponentInfoInitializerDecorator.java.patch, 
> PipelineComponentScope.java.patch, ServletDecorator.java.patch, 
> ServletScope.java.patch, SitemapElementParser.java.patch, 
> SourceResource.java.patch, WildcardBeanMap.java.patch
>
>
> The goal of this ticket is to make the current Cocoon TRUNK of 2.2 compatible 
> with latest Spring Framework version.
> According to research and feedback in mailinglist following projects (maven 
> modules) are affected:
> - cocoon-spring-configurator
> - cocoon-servlet-service-impl
> - cocoon-sitemap-impl
> - cocoon-pipeline-impl
> - cocoon-expression-api
> - cocoon-expression-language-impl
> ..
> Let's discuss problems, and append patches here and someone of the committers 
> can then apply them to SVN.
> Original mail thread: http://markmail.org/message/kkdxrsjqoan6mhr6
> SVN branches:
>  * https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_2_COCOON-2347
>  * 
> https://svn.apache.org/repos/asf/cocoon/subprojects/cocoon-spring-configurator/branches/COCOON-2347
>  * 
> https://svn.apache.org/repos/asf/cocoon/subprojects/cocoon-servlet-service-impl/branches/COCOON-2347
> Jenkins job: https://builds.apache.org/job/Cocoon 2.2



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Comment Edited] (COCOON-2347) Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version

2015-10-31 Thread Javier Puerto (JIRA)

[ 
https://issues.apache.org/jira/browse/COCOON-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14984070#comment-14984070
 ] 

Javier Puerto edited comment on COCOON-2347 at 10/31/15 5:38 PM:
-

No progress yet with the issue. I've run the webapp module and the behaviour is 
very weird, looks like the web contexts are overlapping because I got different 
types of exceptions navigation through the pages.

{quote}
Nested in javax.servlet.ServletException: 
org.apache.cocoon.ProcessingException: Failed to process pipeline
at  - 
file:///media/cache/src/cocoon-2.2-2347/core/cocoon-webapp/target/work/blocks/cocoon-samples-style-default/sitemap.xmap:62:35:
org.apache.cocoon.ProcessingException: Failed to process pipeline
at  - 
file:///media/cache/src/cocoon-2.2-2347/core/cocoon-webapp/target/work/blocks/cocoon-samples-style-default/sitemap.xmap:62:35
at 
org.apache.cocoon.ProcessingException.throwLocated(ProcessingException.java:143)
at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.handleException(AbstractProcessingPipeline.java:940)
at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.setupReader(AbstractProcessingPipeline.java:573)
at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.preparePipeline(AbstractProcessingPipeline.java:469)
at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process(AbstractProcessingPipeline.java:416)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:79)
at com.sun.proxy.$Proxy37.process(Unknown Source)
at 
org.apache.cocoon.components.treeprocessor.sitemap.ReadNode.invoke(ReadNode.java:94)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:55)
at 
org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:87)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:143)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:81)
at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:241)
at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:173)
at 
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:247)
at 
org.apache.cocoon.servlet.RequestProcessor.process(RequestProcessor.java:347)
at 
org.apache.cocoon.servlet.RequestProcessor.service(RequestProcessor.java:169)
at 
org.apache.cocoon.sitemap.SitemapServlet.service(SitemapServlet.java:82)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:302)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
at 
org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:85)
at 
org.apache.cocoon.jnet.URLHandlerFactoryCollector.installURLHandlers(URLHandlerFactoryCollector.java:37)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
at 

[jira] [Commented] (COCOON-2347) Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version

2015-10-31 Thread Javier Puerto (JIRA)

[ 
https://issues.apache.org/jira/browse/COCOON-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14984070#comment-14984070
 ] 

Javier Puerto commented on COCOON-2347:
---

No progress yet with the issue. I've run the webapp module and the behaviour is 
very weird, looks like the web contexts are overlapping because I got different 
types of exceptions navigation through the pages.

{code}
Nested in javax.servlet.ServletException: 
org.apache.cocoon.ProcessingException: Failed to process pipeline
at  - 
file:///media/cache/src/cocoon-2.2-2347/core/cocoon-webapp/target/work/blocks/cocoon-samples-style-default/sitemap.xmap:62:35:
org.apache.cocoon.ProcessingException: Failed to process pipeline
at  - 
file:///media/cache/src/cocoon-2.2-2347/core/cocoon-webapp/target/work/blocks/cocoon-samples-style-default/sitemap.xmap:62:35
at 
org.apache.cocoon.ProcessingException.throwLocated(ProcessingException.java:143)
at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.handleException(AbstractProcessingPipeline.java:940)
at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.setupReader(AbstractProcessingPipeline.java:573)
at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.preparePipeline(AbstractProcessingPipeline.java:469)
at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process(AbstractProcessingPipeline.java:416)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:79)
at com.sun.proxy.$Proxy37.process(Unknown Source)
at 
org.apache.cocoon.components.treeprocessor.sitemap.ReadNode.invoke(ReadNode.java:94)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:55)
at 
org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:87)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:143)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:81)
at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:241)
at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:173)
at 
org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:247)
at 
org.apache.cocoon.servlet.RequestProcessor.process(RequestProcessor.java:347)
at 
org.apache.cocoon.servlet.RequestProcessor.service(RequestProcessor.java:169)
at 
org.apache.cocoon.sitemap.SitemapServlet.service(SitemapServlet.java:82)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:302)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
at 
org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:85)
at 
org.apache.cocoon.jnet.URLHandlerFactoryCollector.installURLHandlers(URLHandlerFactoryCollector.java:37)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
at 
org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)
at 

[jira] [Closed] (COCOON3-127) Buggy 3.0.0-alpha-3 Maven archetypes

2014-05-11 Thread Javier Puerto (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON3-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javier Puerto closed COCOON3-127.
-

Resolution: Fixed

 Buggy 3.0.0-alpha-3 Maven archetypes
 

 Key: COCOON3-127
 URL: https://issues.apache.org/jira/browse/COCOON3-127
 Project: Cocoon 3
  Issue Type: Bug
  Components: cocoon-archetype-X, site
Affects Versions: 3.0.0-alpha-3
Reporter: Francesco Chicchiriccò
Assignee: Francesco Chicchiriccò
 Fix For: 3.0.0-beta-1


 As reported in user ML [1], there are some issues with 3.0.0-alpha-3 Maven 
 archetypes; [2] must report the needed workarounds.
 [1] 
 http://cocoon.10839.n7.nabble.com/XSLT-import-include-errors-tp57999p58060.html
 [2] http://cocoon.apache.org/3.0/download.html



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Closed] (COCOON3-129) Create an example to send a mail via cocoon

2014-05-11 Thread Javier Puerto (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON3-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javier Puerto closed COCOON3-129.
-

Resolution: Fixed

 Create an example to send a mail via cocoon
 ---

 Key: COCOON3-129
 URL: https://issues.apache.org/jira/browse/COCOON3-129
 Project: Cocoon 3
  Issue Type: New Feature
  Components: cocoon-rest-optional
Affects Versions: 3.0.0-beta-1
Reporter: Thorsten Scherler
 Fix For: 3.0.0-beta-1


 http://markmail.org/message/6ces6erwekf57qfo 
 as requested from hansheinrichbraun in above mail I extracted a simple 
 example to send a mail with cocoon based on work of codebusters.es.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Assigned] (COCOON-2340) XMLByteStreamCompiler in not thread-safe

2013-11-30 Thread Javier Puerto (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javier Puerto reassigned COCOON-2340:
-

Assignee: Javier Puerto

 XMLByteStreamCompiler in not thread-safe
 

 Key: COCOON-2340
 URL: https://issues.apache.org/jira/browse/COCOON-2340
 Project: Cocoon
  Issue Type: Bug
  Components: * Cocoon Core
Affects Versions: 2.2
Reporter: Ivan Lagunov
Assignee: Javier Puerto

 I'm periodically getting the following exceptions in different places:
 Caused by: java.lang.ArrayIndexOutOfBoundsException
 at java.lang.System.arraycopy(Native Method)
 at 
 org.apache.cocoon.components.sax.XMLByteStreamCompiler.getSAXFragment(XMLByteStreamCompiler.java:61)
 at 
 org.apache.cocoon.components.pipeline.impl.ExpiresCachingProcessingPipeline.processXMLPipeline(ExpiresCachingProcessingPipeline.java:152)
 After debugging I've found the root cause. It happens due to multi-threading 
 when one thread allocates newbuf array, then another thread increments 
 bufCount in write method and then the first thread fails on System.arraycopy 
 invocation.
 I suggest making getSAXFragment and write methods synchronized. It should 
 resolve the issue. If it helps, I'll provide a patch later.



--
This message was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Commented] (COCOON-2340) XMLByteStreamCompiler in not thread-safe

2013-11-30 Thread Javier Puerto (JIRA)

[ 
https://issues.apache.org/jira/browse/COCOON-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13835758#comment-13835758
 ] 

Javier Puerto commented on COCOON-2340:
---

Hi Ivan,

By the error, you are using a pipeline with expires caching enabled and the 
problem seems to be retrieving an XML fragment (CInclude transformer?). With 
this information I can't investigate further, I've also used with others 
projects the expires caching in pipelines without any concurrency issues so I 
recommend you to provide a small pipeline fragment where the problem can be 
reproduced so we can take a look. Following the advices I've said in the 
previous comment, Apache Cocoon 2.2 should not have any concurrency problems.

To found the possible cause you could use the ab tool (ApacheBench [1]) that 
comes with the Apache HTTPD server. Then comment everything that involves with 
your pipeline leaving just the generator and the serializer and start 
uncommenting and testing with ab tool with high concurrency, this way you can 
isolate the problematic component or pipeline.

Good luck and salu2.

[1] http://httpd.apache.org/docs/2.2/programs/ab.html

 XMLByteStreamCompiler in not thread-safe
 

 Key: COCOON-2340
 URL: https://issues.apache.org/jira/browse/COCOON-2340
 Project: Cocoon
  Issue Type: Bug
  Components: * Cocoon Core
Affects Versions: 2.2
Reporter: Ivan Lagunov

 I'm periodically getting the following exceptions in different places:
 Caused by: java.lang.ArrayIndexOutOfBoundsException
 at java.lang.System.arraycopy(Native Method)
 at 
 org.apache.cocoon.components.sax.XMLByteStreamCompiler.getSAXFragment(XMLByteStreamCompiler.java:61)
 at 
 org.apache.cocoon.components.pipeline.impl.ExpiresCachingProcessingPipeline.processXMLPipeline(ExpiresCachingProcessingPipeline.java:152)
 After debugging I've found the root cause. It happens due to multi-threading 
 when one thread allocates newbuf array, then another thread increments 
 bufCount in write method and then the first thread fails on System.arraycopy 
 invocation.
 I suggest making getSAXFragment and write methods synchronized. It should 
 resolve the issue. If it helps, I'll provide a patch later.



--
This message was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Commented] (COCOON-2338) Port the Cocoon3 TikaGenerator to Cocoon 2.1.13

2013-11-30 Thread Javier Puerto (JIRA)

[ 
https://issues.apache.org/jira/browse/COCOON-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13835761#comment-13835761
 ] 

Javier Puerto commented on COCOON-2338:
---

Hi Dan,

IMO it's should not be difficult to port it, the most complicated stuff will be 
to make it cacheable as the caching system changed in Cocoon 3. I want to port 
it to version 2.2.x when I can found some free time but unfortunately I'm not 
familiar with version 2.1.x. If anyone wants to port it, I could help providing 
support.

 Port the Cocoon3 TikaGenerator to Cocoon 2.1.13
 ---

 Key: COCOON-2338
 URL: https://issues.apache.org/jira/browse/COCOON-2338
 Project: Cocoon
  Issue Type: New Feature
  Components: * Cocoon Core, - Components: Sitemap
Reporter: Dan Hertz
Assignee: Javier Puerto

 How difficult would it be to port the TikaGenerator classes from Cocoon3 to 
 Cocoon 2.1.13?
 Apache Tika is a powerful tool for extracting content and metadata from a 
 wide variety of file formats.
 See: https://issues.apache.org/jira/browse/COCOON3-128
 Unfortunately, I don't have a clue how to do this: is there someone who would 
 like to take the lead?
 Classes are: TikaGenerator.java, and for testing TikaGeneratorTestCase.
 The former's path is:
 cocoon3/trunk/cocoon-optional/src/main/java/org/apache/cocoon/optional/pipeline/components/sax/tika/TikaGenerator.java
 Thanks!
 Dan



--
This message was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Assigned] (COCOON-2338) Port the Cocoon3 TikaGenerator to Cocoon 2.1.13

2013-11-30 Thread Javier Puerto (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javier Puerto reassigned COCOON-2338:
-

Assignee: (was: Javier Puerto)

 Port the Cocoon3 TikaGenerator to Cocoon 2.1.13
 ---

 Key: COCOON-2338
 URL: https://issues.apache.org/jira/browse/COCOON-2338
 Project: Cocoon
  Issue Type: New Feature
  Components: * Cocoon Core, - Components: Sitemap
Reporter: Dan Hertz

 How difficult would it be to port the TikaGenerator classes from Cocoon3 to 
 Cocoon 2.1.13?
 Apache Tika is a powerful tool for extracting content and metadata from a 
 wide variety of file formats.
 See: https://issues.apache.org/jira/browse/COCOON3-128
 Unfortunately, I don't have a clue how to do this: is there someone who would 
 like to take the lead?
 Classes are: TikaGenerator.java, and for testing TikaGeneratorTestCase.
 The former's path is:
 cocoon3/trunk/cocoon-optional/src/main/java/org/apache/cocoon/optional/pipeline/components/sax/tika/TikaGenerator.java
 Thanks!
 Dan



--
This message was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Commented] (COCOON-2340) XMLByteStreamCompiler in not thread-safe

2013-11-28 Thread Javier Puerto (JIRA)

[ 
https://issues.apache.org/jira/browse/COCOON-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13834654#comment-13834654
 ] 

Javier Puerto commented on COCOON-2340:
---

Hi,

I've more familiar with the 2.2 version. I've experienced issues like you 
described and it was by the following reasons, now works like a charm :). So, 
could you check the following?

* The components in the pipeline was declared as singleton instead of 
prototype. Some components are not thread safe, use prototype scope to avoid 
this problem.
* The version 2.2 is using an older version of Apache Xalan. Upgrade to 2.2.1 
or upgrade Xalan to latest, see COCOON-2156.

Anyway, could you provide an example to reproduce the problem if it persists?

Salu2.

 XMLByteStreamCompiler in not thread-safe
 

 Key: COCOON-2340
 URL: https://issues.apache.org/jira/browse/COCOON-2340
 Project: Cocoon
  Issue Type: Bug
  Components: * Cocoon Core
Affects Versions: 2.2
Reporter: Ivan Lagunov

 I'm periodically getting the following exceptions in different places:
 Caused by: java.lang.ArrayIndexOutOfBoundsException
 at java.lang.System.arraycopy(Native Method)
 at 
 org.apache.cocoon.components.sax.XMLByteStreamCompiler.getSAXFragment(XMLByteStreamCompiler.java:61)
 at 
 org.apache.cocoon.components.pipeline.impl.ExpiresCachingProcessingPipeline.processXMLPipeline(ExpiresCachingProcessingPipeline.java:152)
 After debugging I've found the root cause. It happens due to multi-threading 
 when one thread allocates newbuf array, then another thread increments 
 bufCount in write method and then the first thread fails on System.arraycopy 
 invocation.
 I suggest making getSAXFragment and write methods synchronized. It should 
 resolve the issue. If it helps, I'll provide a patch later.



--
This message was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Commented] (COCOON-2340) XMLByteStreamCompiler in not thread-safe

2013-11-28 Thread Javier Puerto (JIRA)

[ 
https://issues.apache.org/jira/browse/COCOON-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13835015#comment-13835015
 ] 

Javier Puerto commented on COCOON-2340:
---

Hi Ivan,

You are right, I thought that the 2.2.1 was released but it's not. You can 
apply the patch from COCOON-2156 to the tag 
http://svn.apache.org/repos/asf/cocoon/tags/cocoon-2.2/
About the singleton components, you can try yourself if you redeclare the 
Cocoon component with a different name and then use this one instead of the 
default one in the core.
Anyway you should provide an example to reproduce the issue so I can take a 
look but I will not be able to review it until the weekend.

Salu2.

 XMLByteStreamCompiler in not thread-safe
 

 Key: COCOON-2340
 URL: https://issues.apache.org/jira/browse/COCOON-2340
 Project: Cocoon
  Issue Type: Bug
  Components: * Cocoon Core
Affects Versions: 2.2
Reporter: Ivan Lagunov

 I'm periodically getting the following exceptions in different places:
 Caused by: java.lang.ArrayIndexOutOfBoundsException
 at java.lang.System.arraycopy(Native Method)
 at 
 org.apache.cocoon.components.sax.XMLByteStreamCompiler.getSAXFragment(XMLByteStreamCompiler.java:61)
 at 
 org.apache.cocoon.components.pipeline.impl.ExpiresCachingProcessingPipeline.processXMLPipeline(ExpiresCachingProcessingPipeline.java:152)
 After debugging I've found the root cause. It happens due to multi-threading 
 when one thread allocates newbuf array, then another thread increments 
 bufCount in write method and then the first thread fails on System.arraycopy 
 invocation.
 I suggest making getSAXFragment and write methods synchronized. It should 
 resolve the issue. If it helps, I'll provide a patch later.



--
This message was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Closed] (COCOON-2339) C:\Program Files\cocoon-2.1.12 src\src\blocks\databases\java\org\apache\cocoon\d atabases\ibatis\ExcaliburDataSourceFactory.java:82: error: DataSourceWrapper is not abstr

2013-10-23 Thread Javier Puerto (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javier Puerto closed COCOON-2339.
-

Resolution: Invalid

 C:\Program Files\cocoon-2.1.12 
 src\src\blocks\databases\java\org\apache\cocoon\d 
 atabases\ibatis\ExcaliburDataSourceFactory.java:82: error: DataSourceWrapper 
 is not abstract and does not override abstract method getParentLogger() in 
 CommonDa taSource 
 ---

 Key: COCOON-2339
 URL: https://issues.apache.org/jira/browse/COCOON-2339
 Project: Cocoon
  Issue Type: Bug
  Components: - Build System: Ant
Reporter: ramakanth allam





--
This message was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Created] (COCOON3-130) Add support for Solr atomic updates

2013-10-08 Thread Javier Puerto (JIRA)
Javier Puerto created COCOON3-130:
-

 Summary: Add support for Solr atomic updates
 Key: COCOON3-130
 URL: https://issues.apache.org/jira/browse/COCOON3-130
 Project: Cocoon 3
  Issue Type: Improvement
  Components: cocoon-optional
Affects Versions: 3.0.0-beta-1
Reporter: Javier Puerto
Priority: Minor


Current SolrConsumer class doesn't takes care about new atomic updates feature 
from Apache Solr. See 
http://wiki.apache.org/solr/UpdateXmlMessages#Optional_attributes_for_.22field.22

At the moment, any attempt to do an atomic update ends with an overwritten 
document as the transformer doesn't care about the new attributes defined in 
version 4.x.



--
This message was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Closed] (COCOON3-128) Add Apache Tika support

2013-07-20 Thread Javier Puerto (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON3-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javier Puerto closed COCOON3-128.
-

Resolution: Fixed

As I usually start with plain block archetype, I didn't realized that the 
sample archetype recreates the samples block. I've updated the code so Tika 
samples can works without problems. I've also added the dependency to parent 
archetype.

 Add Apache Tika support
 ---

 Key: COCOON3-128
 URL: https://issues.apache.org/jira/browse/COCOON3-128
 Project: Cocoon 3
  Issue Type: New Feature
  Components: cocoon-optional
Affects Versions: 3.0.0-beta-1
Reporter: Javier Puerto
Assignee: Javier Puerto
 Fix For: 3.0.0


 Apache Tika is an excelent parser several documents formats. Create a 
 generator that use default Tika configuration and put the resulting SAX 
 events into the pipeline.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Reopened] (COCOON3-128) Add Apache Tika support

2013-07-17 Thread Javier Puerto (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON3-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javier Puerto reopened COCOON3-128:
---


Thanks Francesco, I didn't noticed it. I will review and update the Maven 
archetypes resources.

 Add Apache Tika support
 ---

 Key: COCOON3-128
 URL: https://issues.apache.org/jira/browse/COCOON3-128
 Project: Cocoon 3
  Issue Type: New Feature
  Components: cocoon-optional
Affects Versions: 3.0.0-beta-1
Reporter: Javier Puerto
Assignee: Javier Puerto
 Fix For: 3.0.0


 Apache Tika is an excelent parser several documents formats. Create a 
 generator that use default Tika configuration and put the resulting SAX 
 events into the pipeline.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (COCOON3-128) Add Apache Tika support

2013-07-16 Thread Javier Puerto (JIRA)

[ 
https://issues.apache.org/jira/browse/COCOON3-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13710032#comment-13710032
 ] 

Javier Puerto commented on COCOON3-128:
---

PDF test failed to pass because control XML contains a localized date. I've 
removed the problematic value from control file and filtered with an XSLT 
transformation the Tika produced document.

 Add Apache Tika support
 ---

 Key: COCOON3-128
 URL: https://issues.apache.org/jira/browse/COCOON3-128
 Project: Cocoon 3
  Issue Type: New Feature
  Components: cocoon-optional
Affects Versions: 3.0.0-beta-1
Reporter: Javier Puerto
Assignee: Javier Puerto
 Fix For: 3.0.0


 Apache Tika is an excelent parser several documents formats. Create a 
 generator that use default Tika configuration and put the resulting SAX 
 events into the pipeline.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Reopened] (COCOON3-128) Add Apache Tika support

2013-07-14 Thread Javier Puerto (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON3-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javier Puerto reopened COCOON3-128:
---


It's working OK on local tests but the diff seems to be related to the 
different XML element order produced for Jenkins machine. Needs to be updated 
with ElementQualifier feature of the XMLUnit framework.

See: 
http://xmlunit.sourceforge.net/userguide/html/ar01s03.html#ElementQualifier

 Add Apache Tika support
 ---

 Key: COCOON3-128
 URL: https://issues.apache.org/jira/browse/COCOON3-128
 Project: Cocoon 3
  Issue Type: New Feature
  Components: cocoon-optional
Affects Versions: 3.0.0-beta-1
Reporter: Javier Puerto
Assignee: Javier Puerto
 Fix For: 3.0.0


 Apache Tika is an excelent parser several documents formats. Create a 
 generator that use default Tika configuration and put the resulting SAX 
 events into the pipeline.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Closed] (COCOON3-128) Add Apache Tika support

2013-07-14 Thread Javier Puerto (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON3-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javier Puerto closed COCOON3-128.
-

Resolution: Fixed

It should be fixed now. The comparison doesn't takes care of the element nodes 
order but I wasn't able to request a rebuild for Cocoon Jenkins job so we have 
to wait until it triggers itself.

 Add Apache Tika support
 ---

 Key: COCOON3-128
 URL: https://issues.apache.org/jira/browse/COCOON3-128
 Project: Cocoon 3
  Issue Type: New Feature
  Components: cocoon-optional
Affects Versions: 3.0.0-beta-1
Reporter: Javier Puerto
Assignee: Javier Puerto
 Fix For: 3.0.0


 Apache Tika is an excelent parser several documents formats. Create a 
 generator that use default Tika configuration and put the resulting SAX 
 events into the pipeline.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Created] (COCOON3-128) Add Apache Tika support

2013-07-12 Thread Javier Puerto (JIRA)
Javier Puerto created COCOON3-128:
-

 Summary: Add Apache Tika support
 Key: COCOON3-128
 URL: https://issues.apache.org/jira/browse/COCOON3-128
 Project: Cocoon 3
  Issue Type: New Feature
  Components: cocoon-optional
Affects Versions: 3.0.0-beta-1
Reporter: Javier Puerto
Assignee: Javier Puerto
 Fix For: 3.0.0


Apache Tika is an excelent parser several documents formats. Create a generator 
that use default Tika configuration and put the resulting SAX events into the 
pipeline.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Closed] (COCOON3-128) Add Apache Tika support

2013-07-12 Thread Javier Puerto (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON3-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javier Puerto closed COCOON3-128.
-

Resolution: Fixed

r1502623

* Add TikaGenerator class.
* Provide some test cases.

r1502625

* Add Tika examples to samples block.

 Add Apache Tika support
 ---

 Key: COCOON3-128
 URL: https://issues.apache.org/jira/browse/COCOON3-128
 Project: Cocoon 3
  Issue Type: New Feature
  Components: cocoon-optional
Affects Versions: 3.0.0-beta-1
Reporter: Javier Puerto
Assignee: Javier Puerto
 Fix For: 3.0.0


 Apache Tika is an excelent parser several documents formats. Create a 
 generator that use default Tika configuration and put the resulting SAX 
 events into the pipeline.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (COCOON-2325) jx:forEach... returns exactly one item from non-empty collection under jdk 1.6.0_23+

2012-08-13 Thread Javier Puerto (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javier Puerto updated COCOON-2325:
--

Attachment: COCOON-2325.jmx
COCOON-2325.tgz

Attached files for issue testing.

* COCOON-2325.tgz is a sample Apache Cocoon 2.2 block with the usecase 
described in the issue.
* COCOON-2325.jmx is an Apache JMeter functional test that will ask for 
generated flow page and check for response size.

 jx:forEach... returns exactly one item from non-empty collection under jdk 
 1.6.0_23+
 --

 Key: COCOON-2325
 URL: https://issues.apache.org/jira/browse/COCOON-2325
 Project: Cocoon
  Issue Type: Bug
  Components: Blocks: Templating
Affects Versions: 2.2
Reporter: Vasily E. Moskaljov
Assignee: Javier Puerto
 Attachments: COCOON-2325.jmx, COCOON-2325.tgz


 When cocoon 2.2 running on jdk 1.6.0_23+ in some circumstances 
 jx:forEach... constantly return only first value from any non-empty 
 collection.
 Not affected in jdk 1.6.0_18 and lower.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (COCOON-2325) jx:forEach... returns exactly one item from non-empty collection under jdk 1.6.0_23+

2012-08-13 Thread Javier Puerto (JIRA)

[ 
https://issues.apache.org/jira/browse/COCOON-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13433086#comment-13433086
 ] 

Javier Puerto commented on COCOON-2325:
---

I was unable to reproduce the issue with:

java version 1.6.0_20
Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode)

nor

java version 1.7.0_05
Java(TM) SE Runtime Environment (build 1.7.0_05-b05)
Java HotSpot(TM) 64-Bit Server VM (build 23.1-b03, mixed mode)

Attached is the files I used to try to reproduce the issue, maybe it's not the 
correct JDK. Could you try to reproduce the issue with the samples attached?
About the concurrency issue, maybe you can take a look at COCOON-2156. This 
patch is not applied to Apache Cocoon 2.2 TAG is only applied to trunk branch. 
I've experienced wrong behaviour with high concurrency with the old Apache 
Xalan, could you confirm that you are using latest version (2.7.1)?

 jx:forEach... returns exactly one item from non-empty collection under jdk 
 1.6.0_23+
 --

 Key: COCOON-2325
 URL: https://issues.apache.org/jira/browse/COCOON-2325
 Project: Cocoon
  Issue Type: Bug
  Components: Blocks: Templating
Affects Versions: 2.2
Reporter: Vasily E. Moskaljov
Assignee: Javier Puerto
 Attachments: COCOON-2325.jmx, COCOON-2325.tgz


 When cocoon 2.2 running on jdk 1.6.0_23+ in some circumstances 
 jx:forEach... constantly return only first value from any non-empty 
 collection.
 Not affected in jdk 1.6.0_18 and lower.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Closed] (COCOON-2328) Update LocaleAction test case

2012-08-08 Thread Javier Puerto (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javier Puerto closed COCOON-2328.
-

   Resolution: Fixed
Fix Version/s: 2.1.12-dev (Current SVN)

Commited revision: r1370695

In addition to COCOON-2327 it's possible to build Cocoon with JDK 1.7.

 Update LocaleAction test case
 -

 Key: COCOON-2328
 URL: https://issues.apache.org/jira/browse/COCOON-2328
 Project: Cocoon
  Issue Type: Improvement
  Components: * Cocoon Core
Reporter: Javier Puerto
Assignee: Javier Puerto
Priority: Minor
 Fix For: 2.1.12-dev (Current SVN)

 Attachments: COCOON-2328.patch


 For new JDK 1.7, there's a couple of exceptions:
 http://docs.oracle.com/javase/7/docs/api/java/util/Locale.html#special_cases_constructor
  
 As we use the Thailand locale in test case, we need to update the test case 
 to take care about these exceptions.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Closed] (COCOON-2327) Remove use of old com.sun.image.* package from ImageReader

2012-08-08 Thread Javier Puerto (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javier Puerto closed COCOON-2327.
-

Resolution: Fixed

Commited revision: r1370694

Removed conditional code for use in JVM lower than 1.5 as Cocoon 2.2 is for 1.5 
or higher versions.
Change old implementation of image reader for new ImageIO for compatibility 
with JDK 1.7. I've tested with 1.5 and 1.6, the samples block can display all 
the image samples with the new implementation.

 Remove use of old com.sun.image.* package from ImageReader
 --

 Key: COCOON-2327
 URL: https://issues.apache.org/jira/browse/COCOON-2327
 Project: Cocoon
  Issue Type: Improvement
  Components: * Cocoon Core
Affects Versions: 2.2-dev (Current SVN)
Reporter: Javier Puerto
Assignee: Javier Puerto
 Attachments: COCOON-2327.patch


 The use of the package com.sun.image.* is discouraged and it's not supported 
 for JDK 1.7. As we require java version 1.5, we can use Java Image I/O API. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Created] (COCOON-2327) Remove use of old com.sun.image.* package from ImageReader

2012-08-07 Thread Javier Puerto (JIRA)
Javier Puerto created COCOON-2327:
-

 Summary: Remove use of old com.sun.image.* package from ImageReader
 Key: COCOON-2327
 URL: https://issues.apache.org/jira/browse/COCOON-2327
 Project: Cocoon
  Issue Type: Improvement
  Components: * Cocoon Core
Affects Versions: 2.2-dev (Current SVN)
Reporter: Javier Puerto
Assignee: Javier Puerto


The use of the package com.sun.image.* is discouraged and it's not supported 
for JDK 1.7. As we require java version 1.5, we can use Java Image I/O API. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (COCOON-2327) Remove use of old com.sun.image.* package from ImageReader

2012-08-07 Thread Javier Puerto (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javier Puerto updated COCOON-2327:
--

Attachment: COCOON-2327.patch

I'm unable to commit on Cocoon 2.2 repository ATM

 Remove use of old com.sun.image.* package from ImageReader
 --

 Key: COCOON-2327
 URL: https://issues.apache.org/jira/browse/COCOON-2327
 Project: Cocoon
  Issue Type: Improvement
  Components: * Cocoon Core
Affects Versions: 2.2-dev (Current SVN)
Reporter: Javier Puerto
Assignee: Javier Puerto
 Attachments: COCOON-2327.patch


 The use of the package com.sun.image.* is discouraged and it's not supported 
 for JDK 1.7. As we require java version 1.5, we can use Java Image I/O API. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Created] (COCOON-2328) Update LocaleAction test case

2012-08-07 Thread Javier Puerto (JIRA)
Javier Puerto created COCOON-2328:
-

 Summary: Update LocaleAction test case
 Key: COCOON-2328
 URL: https://issues.apache.org/jira/browse/COCOON-2328
 Project: Cocoon
  Issue Type: Improvement
  Components: * Cocoon Core
Reporter: Javier Puerto
Assignee: Javier Puerto
Priority: Minor


For new JDK 1.7, there's a couple of exceptions:
http://docs.oracle.com/javase/7/docs/api/java/util/Locale.html#special_cases_constructor
 

As we use the Thailand locale in test case, we need to update the test case to 
take care about these exceptions.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (COCOON-2328) Update LocaleAction test case

2012-08-07 Thread Javier Puerto (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javier Puerto updated COCOON-2328:
--

Attachment: COCOON-2328.patch

I'm not able to commit to subversion repo yet. Patch with the updated test case.

 Update LocaleAction test case
 -

 Key: COCOON-2328
 URL: https://issues.apache.org/jira/browse/COCOON-2328
 Project: Cocoon
  Issue Type: Improvement
  Components: * Cocoon Core
Reporter: Javier Puerto
Assignee: Javier Puerto
Priority: Minor
 Attachments: COCOON-2328.patch


 For new JDK 1.7, there's a couple of exceptions:
 http://docs.oracle.com/javase/7/docs/api/java/util/Locale.html#special_cases_constructor
  
 As we use the Thailand locale in test case, we need to update the test case 
 to take care about these exceptions.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Closed] (COCOON-2324) Cocoon 2 - Resource not found

2012-07-23 Thread Javier Puerto (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javier Puerto closed COCOON-2324.
-

Resolution: Implemented

 Cocoon 2 - Resource not found
 -

 Key: COCOON-2324
 URL: https://issues.apache.org/jira/browse/COCOON-2324
 Project: Cocoon
  Issue Type: Improvement
  Components: - Components: Sitemap
Affects Versions: 2.1.11
Reporter: Sridhar Goranti
 Fix For: 2.1.11

 Attachments: Cocoon2.1.11 - Resource not found.jpeg


 Hi, 
 I have deployed my cocoon 2.1.11 web application successfully in JBoss 5.1.0 
 GA application server. But when I try access the cocoon application from 
 Internet Explorer browser, I am getting below message:-
 Cocoon 2 - Resource not found
 
 type resource-not-found
 message Resource not found
 description The requested URI 
 /RamsReport/mount/xreporter/en-US/reportcatalog was not found.
 sender org.apache.cocoon.servlet.CocoonServlet
 source Cocoon servlet
 path-info
 mount/xreporter/en-US/reportcatalog
 request-uri
 /RamsReport/mount/xreporter/en-US/reportcatalog
 JBoss 5.1.0 GA Server console log message:-
 ++
 ERROR   (2012-07-17) 14:08.43:214   [sitemap] 
 (/RamsReport/mount/xreporter/en-US/reportcatalog) 
 http-localhost%2F127.0.0.1-8080-5/DefaultTreeBuilder: Failed to load sitemap 
 from 
 file:/C:/RamsReportFinal_Workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_5.1_Runtime_1_Server1342385312791/deploy/RamsReport.war/sitemap.xmap
 org.apache.cocoon.ResourceNotFoundException: Resource not found 
 file:/C:/RamsReportFinal_Workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_5.1_Runtime_1_Server1342385312791/deploy/RamsReport.war/sitemap.xmap:
  java.io.FileNotFoundException: 
 C:\RamsReportFinal_Workspace\.metadata\.plugins\org.jboss.ide.eclipse.as.core\JBoss_5.1_Runtime_1_Server1342385312791\deploy\RamsReport.war\sitemap.xmap
  (The system cannot find the file specified)
   at 
 org.apache.cocoon.components.source.FileSource.getInputStream(FileSource.java:145)
   at 
 org.apache.cocoon.components.source.AbstractStreamSource.getInputSource(AbstractStreamSource.java:161)
   at 
 org.apache.cocoon.components.source.AbstractStreamSource.toSAX(AbstractStreamSource.java:206)
   at 
 org.apache.cocoon.components.source.DelayedRefreshSourceWrapper.toSAX(DelayedRefreshSourceWrapper.java:156)
   at 
 org.apache.cocoon.components.treeprocessor.DefaultTreeBuilder.build(DefaultTreeBuilder.java:387)
   at 
 org.apache.cocoon.components.treeprocessor.TreeProcessor.setupRootNode(TreeProcessor.java:366)
   at 
 org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:330)
   at 
 org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:293)
   at org.apache.cocoon.Cocoon.process(Cocoon.java:579)
   at 
 org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1043)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at 
 org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
   at 
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
   at 
 org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
   at 
 org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
   at 
 org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
   at 
 org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
   at 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
   at 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
   at 
 org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
   at 
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
   at 
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
   at 
 

[jira] [Assigned] (COCOON-2324) Cocoon 2 - Resource not found

2012-07-23 Thread Javier Puerto (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javier Puerto reassigned COCOON-2324:
-

Assignee: Javier Puerto

 Cocoon 2 - Resource not found
 -

 Key: COCOON-2324
 URL: https://issues.apache.org/jira/browse/COCOON-2324
 Project: Cocoon
  Issue Type: Improvement
  Components: - Components: Sitemap
Affects Versions: 2.1.11
Reporter: Sridhar Goranti
Assignee: Javier Puerto
 Fix For: 2.1.11

 Attachments: Cocoon2.1.11 - Resource not found.jpeg


 Hi, 
 I have deployed my cocoon 2.1.11 web application successfully in JBoss 5.1.0 
 GA application server. But when I try access the cocoon application from 
 Internet Explorer browser, I am getting below message:-
 Cocoon 2 - Resource not found
 
 type resource-not-found
 message Resource not found
 description The requested URI 
 /RamsReport/mount/xreporter/en-US/reportcatalog was not found.
 sender org.apache.cocoon.servlet.CocoonServlet
 source Cocoon servlet
 path-info
 mount/xreporter/en-US/reportcatalog
 request-uri
 /RamsReport/mount/xreporter/en-US/reportcatalog
 JBoss 5.1.0 GA Server console log message:-
 ++
 ERROR   (2012-07-17) 14:08.43:214   [sitemap] 
 (/RamsReport/mount/xreporter/en-US/reportcatalog) 
 http-localhost%2F127.0.0.1-8080-5/DefaultTreeBuilder: Failed to load sitemap 
 from 
 file:/C:/RamsReportFinal_Workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_5.1_Runtime_1_Server1342385312791/deploy/RamsReport.war/sitemap.xmap
 org.apache.cocoon.ResourceNotFoundException: Resource not found 
 file:/C:/RamsReportFinal_Workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_5.1_Runtime_1_Server1342385312791/deploy/RamsReport.war/sitemap.xmap:
  java.io.FileNotFoundException: 
 C:\RamsReportFinal_Workspace\.metadata\.plugins\org.jboss.ide.eclipse.as.core\JBoss_5.1_Runtime_1_Server1342385312791\deploy\RamsReport.war\sitemap.xmap
  (The system cannot find the file specified)
   at 
 org.apache.cocoon.components.source.FileSource.getInputStream(FileSource.java:145)
   at 
 org.apache.cocoon.components.source.AbstractStreamSource.getInputSource(AbstractStreamSource.java:161)
   at 
 org.apache.cocoon.components.source.AbstractStreamSource.toSAX(AbstractStreamSource.java:206)
   at 
 org.apache.cocoon.components.source.DelayedRefreshSourceWrapper.toSAX(DelayedRefreshSourceWrapper.java:156)
   at 
 org.apache.cocoon.components.treeprocessor.DefaultTreeBuilder.build(DefaultTreeBuilder.java:387)
   at 
 org.apache.cocoon.components.treeprocessor.TreeProcessor.setupRootNode(TreeProcessor.java:366)
   at 
 org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:330)
   at 
 org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:293)
   at org.apache.cocoon.Cocoon.process(Cocoon.java:579)
   at 
 org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1043)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at 
 org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
   at 
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
   at 
 org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
   at 
 org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
   at 
 org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
   at 
 org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
   at 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
   at 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
   at 
 org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
   at 
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
   at 
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
   at 
 

[jira] [Commented] (COCOON-2324) Cocoon 2 - Resource not found

2012-07-23 Thread Javier Puerto (JIRA)

[ 
https://issues.apache.org/jira/browse/COCOON-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420753#comment-13420753
 ] 

Javier Puerto commented on COCOON-2324:
---

By latest email messages from dev list, seems like the user fixed this issue. 
http://cocoon.markmail.org/thread/jgu6flwamn7fvpe4

 Cocoon 2 - Resource not found
 -

 Key: COCOON-2324
 URL: https://issues.apache.org/jira/browse/COCOON-2324
 Project: Cocoon
  Issue Type: Improvement
  Components: - Components: Sitemap
Affects Versions: 2.1.11
Reporter: Sridhar Goranti
Assignee: Javier Puerto
 Fix For: 2.1.11

 Attachments: Cocoon2.1.11 - Resource not found.jpeg


 Hi, 
 I have deployed my cocoon 2.1.11 web application successfully in JBoss 5.1.0 
 GA application server. But when I try access the cocoon application from 
 Internet Explorer browser, I am getting below message:-
 Cocoon 2 - Resource not found
 
 type resource-not-found
 message Resource not found
 description The requested URI 
 /RamsReport/mount/xreporter/en-US/reportcatalog was not found.
 sender org.apache.cocoon.servlet.CocoonServlet
 source Cocoon servlet
 path-info
 mount/xreporter/en-US/reportcatalog
 request-uri
 /RamsReport/mount/xreporter/en-US/reportcatalog
 JBoss 5.1.0 GA Server console log message:-
 ++
 ERROR   (2012-07-17) 14:08.43:214   [sitemap] 
 (/RamsReport/mount/xreporter/en-US/reportcatalog) 
 http-localhost%2F127.0.0.1-8080-5/DefaultTreeBuilder: Failed to load sitemap 
 from 
 file:/C:/RamsReportFinal_Workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_5.1_Runtime_1_Server1342385312791/deploy/RamsReport.war/sitemap.xmap
 org.apache.cocoon.ResourceNotFoundException: Resource not found 
 file:/C:/RamsReportFinal_Workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_5.1_Runtime_1_Server1342385312791/deploy/RamsReport.war/sitemap.xmap:
  java.io.FileNotFoundException: 
 C:\RamsReportFinal_Workspace\.metadata\.plugins\org.jboss.ide.eclipse.as.core\JBoss_5.1_Runtime_1_Server1342385312791\deploy\RamsReport.war\sitemap.xmap
  (The system cannot find the file specified)
   at 
 org.apache.cocoon.components.source.FileSource.getInputStream(FileSource.java:145)
   at 
 org.apache.cocoon.components.source.AbstractStreamSource.getInputSource(AbstractStreamSource.java:161)
   at 
 org.apache.cocoon.components.source.AbstractStreamSource.toSAX(AbstractStreamSource.java:206)
   at 
 org.apache.cocoon.components.source.DelayedRefreshSourceWrapper.toSAX(DelayedRefreshSourceWrapper.java:156)
   at 
 org.apache.cocoon.components.treeprocessor.DefaultTreeBuilder.build(DefaultTreeBuilder.java:387)
   at 
 org.apache.cocoon.components.treeprocessor.TreeProcessor.setupRootNode(TreeProcessor.java:366)
   at 
 org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:330)
   at 
 org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:293)
   at org.apache.cocoon.Cocoon.process(Cocoon.java:579)
   at 
 org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1043)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at 
 org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
   at 
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
   at 
 org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
   at 
 org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
   at 
 org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
   at 
 org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
   at 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
   at 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
   at 
 org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
   at 
 

[jira] [Commented] (COCOON-2325) jx:forEach... returns exactly one item from non-empty collection under jdk 1.6.0_23+

2012-07-23 Thread Javier Puerto (JIRA)

[ 
https://issues.apache.org/jira/browse/COCOON-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13420760#comment-13420760
 ] 

Javier Puerto commented on COCOON-2325:
---

Hello Vasily,

I've worked with JX flow and I had some weird issues sometimes but I never had 
this one. Could you attach an example block or the problematic code to 
reproduce?

 jx:forEach... returns exactly one item from non-empty collection under jdk 
 1.6.0_23+
 --

 Key: COCOON-2325
 URL: https://issues.apache.org/jira/browse/COCOON-2325
 Project: Cocoon
  Issue Type: Bug
  Components: Blocks: Templating
Affects Versions: 2.2
Reporter: Vasily E. Moskaljov

 When cocoon 2.2 running on jdk 1.6.0_23+ in some circumstances 
 jx:forEach... constantly return only first value from any non-empty 
 collection.
 Not affected in jdk 1.6.0_18 and lower.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Assigned] (COCOON-2325) jx:forEach... returns exactly one item from non-empty collection under jdk 1.6.0_23+

2012-07-23 Thread Javier Puerto (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javier Puerto reassigned COCOON-2325:
-

Assignee: Javier Puerto

 jx:forEach... returns exactly one item from non-empty collection under jdk 
 1.6.0_23+
 --

 Key: COCOON-2325
 URL: https://issues.apache.org/jira/browse/COCOON-2325
 Project: Cocoon
  Issue Type: Bug
  Components: Blocks: Templating
Affects Versions: 2.2
Reporter: Vasily E. Moskaljov
Assignee: Javier Puerto

 When cocoon 2.2 running on jdk 1.6.0_23+ in some circumstances 
 jx:forEach... constantly return only first value from any non-empty 
 collection.
 Not affected in jdk 1.6.0_18 and lower.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (COCOON-2325) jx:forEach... returns exactly one item from non-empty collection under jdk 1.6.0_23+

2012-07-23 Thread Javier Puerto (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javier Puerto updated COCOON-2325:
--

Status: On Hold  (was: Open)

 jx:forEach... returns exactly one item from non-empty collection under jdk 
 1.6.0_23+
 --

 Key: COCOON-2325
 URL: https://issues.apache.org/jira/browse/COCOON-2325
 Project: Cocoon
  Issue Type: Bug
  Components: Blocks: Templating
Affects Versions: 2.2
Reporter: Vasily E. Moskaljov
Assignee: Javier Puerto

 When cocoon 2.2 running on jdk 1.6.0_23+ in some circumstances 
 jx:forEach... constantly return only first value from any non-empty 
 collection.
 Not affected in jdk 1.6.0_18 and lower.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Closed] (COCOON-2323) Cocoon 2 - Resource not found

2012-07-17 Thread Javier Puerto (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON-2323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javier Puerto closed COCOON-2323.
-

Resolution: Duplicate

Duplicate from COCOON-2324

 Cocoon 2 - Resource not found
 -

 Key: COCOON-2323
 URL: https://issues.apache.org/jira/browse/COCOON-2323
 Project: Cocoon
  Issue Type: Improvement
  Components: - Components: Sitemap
Affects Versions: 2.1.11
Reporter: Sridhar Goranti
Priority: Critical
 Attachments: Cocoon2.1.11 - Resource not found.jpeg


 Hi,
 I have deployed my cocoon 2.1.11 application in JBoss 5.1.0 GA application 
 server. When I tried to access my application from Internet Explorer browser, 
 I am getting below message :-
 Cocoon 2 - Resource not found
 
 type resource-not-found
 message Resource not found
 description The requested URI 
 /RamsReport/mount/xreporter/en-US/reportcatalog was not found.
 sender org.apache.cocoon.servlet.CocoonServlet
 source Cocoon servlet
 path-info
 mount/xreporter/en-US/reportcatalog
 request-uri
 /RamsReport/mount/xreporter/en-US/reportcatalog
 Note: In this application I am using JDK 1.6 and JBoss 5.1.0 GA Application 
 Server
 If anybody worked on and come across, please help me here.
 Thanks  Regards,
 Sridhar Goranti
  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (COCOON-2324) Cocoon 2 - Resource not found

2012-07-17 Thread Javier Puerto (JIRA)

[ 
https://issues.apache.org/jira/browse/COCOON-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13416537#comment-13416537
 ] 

Javier Puerto commented on COCOON-2324:
---

Hi Sridhar

Please, use the mailing user list to ask if you have any problem first. You can 
check the following page: http://cocoon.apache.org/2.1/1175.html#Cocoon+Users
The user list is read by more people so you can found more help, JIRA is more 
for developers.

Regarding your problem, seems like Cocoon can't found the sitemap.xmap file to 
process your request. Could you confirm if the file 
C:/RamsReportFinal_Workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_5.1_Runtime_1_Server1342385312791/deploy/RamsReport.war/sitemap.xmap
  exists?

Salu2.

 Cocoon 2 - Resource not found
 -

 Key: COCOON-2324
 URL: https://issues.apache.org/jira/browse/COCOON-2324
 Project: Cocoon
  Issue Type: Improvement
  Components: - Components: Sitemap
Affects Versions: 2.1.11
Reporter: Sridhar Goranti
 Fix For: 2.1.11

 Attachments: Cocoon2.1.11 - Resource not found.jpeg


 Hi, 
 I have deployed my cocoon 2.1.11 web application successfully in JBoss 5.1.0 
 GA application server. But when I try access the cocoon application from 
 Internet Explorer browser, I am getting below message:-
 Cocoon 2 - Resource not found
 
 type resource-not-found
 message Resource not found
 description The requested URI 
 /RamsReport/mount/xreporter/en-US/reportcatalog was not found.
 sender org.apache.cocoon.servlet.CocoonServlet
 source Cocoon servlet
 path-info
 mount/xreporter/en-US/reportcatalog
 request-uri
 /RamsReport/mount/xreporter/en-US/reportcatalog
 JBoss 5.1.0 GA Server console log message:-
 ++
 ERROR   (2012-07-17) 14:08.43:214   [sitemap] 
 (/RamsReport/mount/xreporter/en-US/reportcatalog) 
 http-localhost%2F127.0.0.1-8080-5/DefaultTreeBuilder: Failed to load sitemap 
 from 
 file:/C:/RamsReportFinal_Workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_5.1_Runtime_1_Server1342385312791/deploy/RamsReport.war/sitemap.xmap
 org.apache.cocoon.ResourceNotFoundException: Resource not found 
 file:/C:/RamsReportFinal_Workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/JBoss_5.1_Runtime_1_Server1342385312791/deploy/RamsReport.war/sitemap.xmap:
  java.io.FileNotFoundException: 
 C:\RamsReportFinal_Workspace\.metadata\.plugins\org.jboss.ide.eclipse.as.core\JBoss_5.1_Runtime_1_Server1342385312791\deploy\RamsReport.war\sitemap.xmap
  (The system cannot find the file specified)
   at 
 org.apache.cocoon.components.source.FileSource.getInputStream(FileSource.java:145)
   at 
 org.apache.cocoon.components.source.AbstractStreamSource.getInputSource(AbstractStreamSource.java:161)
   at 
 org.apache.cocoon.components.source.AbstractStreamSource.toSAX(AbstractStreamSource.java:206)
   at 
 org.apache.cocoon.components.source.DelayedRefreshSourceWrapper.toSAX(DelayedRefreshSourceWrapper.java:156)
   at 
 org.apache.cocoon.components.treeprocessor.DefaultTreeBuilder.build(DefaultTreeBuilder.java:387)
   at 
 org.apache.cocoon.components.treeprocessor.TreeProcessor.setupRootNode(TreeProcessor.java:366)
   at 
 org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:330)
   at 
 org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:293)
   at org.apache.cocoon.Cocoon.process(Cocoon.java:579)
   at 
 org.apache.cocoon.servlet.CocoonServlet.service(CocoonServlet.java:1043)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at 
 org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
   at 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
   at 
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
   at 
 org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
   at 
 org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
   at 
 org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
   at 
 

[jira] [Commented] (COCOON3-102) The org.apache.cocoon.sax.component.XIncludeTransformer is not cacheable

2012-06-20 Thread Javier Puerto (JIRA)

[ 
https://issues.apache.org/jira/browse/COCOON3-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13397580#comment-13397580
 ] 

Javier Puerto commented on COCOON3-102:
---

You are right, with current implementation it's very difficult to achieve this 
tasks but it's possible with the patch I did for COCOON3-100. Anyway, I didn't 
commited yet because I'm not entirely happy with the URLCacheKey 
implementation, the expires that you commented could be used in that class. ATM 
I don't have enough time to work with Cocoon 3 until this weekend so if you 
have, you could take a look and improve it.

 The org.apache.cocoon.sax.component.XIncludeTransformer is not cacheable
 

 Key: COCOON3-102
 URL: https://issues.apache.org/jira/browse/COCOON3-102
 Project: Cocoon 3
  Issue Type: Improvement
  Components: cocoon-sax
Affects Versions: 3.0.0-alpha-3
Reporter: Simone Tripodi
Assignee: Francesco Chicchiriccò
 Fix For: 3.0.0-beta-1

 Attachments: COCOON3-102.patch


 The org.apache.cocoon.sax.component.XIncludeTransformer is not a cacheable 
 pipeline component, it would be great to implement it as cacheable

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (COCOON3-102) The org.apache.cocoon.sax.component.XIncludeTransformer is not cacheable

2012-06-20 Thread Javier Puerto (JIRA)

[ 
https://issues.apache.org/jira/browse/COCOON3-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13397606#comment-13397606
 ] 

Javier Puerto commented on COCOON3-102:
---

The patch is working but the problem is that COCOON3-30 is blocking the issue. 
Summarizing:

As you pointed, I use a similar approach as old Cocoon 2.x does. I've created a 
CachedCacheKey that will store the CacheKey for a given key. First time 
IncludeTransformer is executed, the CacheKey is created and stored in the 
CachingCacheKey object in a Cache (SimpleCache implementation) with a given key 
(usually the request URL). Next time, that Cocoon ask for the CacheKey, it will 
be checked with the cached one.

The problem is the following, we use double check for caching: etag and last 
modified. If etag matches, we don't check the last-modified value (it's 
cached), otherwise Cocoon check the last-modified (here COCOON3-30 is breaking 
the caching). In the sample block for IncludeTransformer we have the same file 
included twice, but the difference is that one use the file:// protocol and the 
other uses the servlet:// protocol. URLCacheKey will check the etag and 
last-modified values, but the file:// implementation don't provide the etag 
information so Cocoon use last-modified as fallback and finally 
ParameterCacheKey breaks the cache.

You can test it easily with the sample block and changing the ParameterCacheKey 
value of last-modified to 0 for example, this way will work at least for 
testing. I had some improvements in local but I'm still not happy with the 
URLCacheKey impl.

I've commented the problem to Thorsten and he suggest that maybe we could 
migrate the SourceValidity from old Cocoon implementation. IMO the caching 
system from old Cocoon was OK, so I'm agree with him but means that we should 
have to change a lot of things. WDYT?

 The org.apache.cocoon.sax.component.XIncludeTransformer is not cacheable
 

 Key: COCOON3-102
 URL: https://issues.apache.org/jira/browse/COCOON3-102
 Project: Cocoon 3
  Issue Type: Improvement
  Components: cocoon-sax
Affects Versions: 3.0.0-alpha-3
Reporter: Simone Tripodi
Assignee: Francesco Chicchiriccò
 Fix For: 3.0.0-beta-1

 Attachments: COCOON3-102.patch


 The org.apache.cocoon.sax.component.XIncludeTransformer is not a cacheable 
 pipeline component, it would be great to implement it as cacheable

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (COCOON3-76) Remove jakarta-regexp dependency

2012-05-21 Thread Javier Puerto (JIRA)

[ 
https://issues.apache.org/jira/browse/COCOON3-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13280021#comment-13280021
 ] 

Javier Puerto commented on COCOON3-76:
--

IMO matches method makes more sense, less ambiguity and also it's the 
behaviour I should expect. The problem is the backwards compatibility.

 Remove jakarta-regexp dependency
 

 Key: COCOON3-76
 URL: https://issues.apache.org/jira/browse/COCOON3-76
 Project: Cocoon 3
  Issue Type: Improvement
  Components: cocoon-optional
Affects Versions: 3.0.0-beta-1
Reporter: Francesco Chicchiriccò
Assignee: Francesco Chicchiriccò
 Fix For: 3.0.0-beta-1

 Attachments: COCOON3-76-find.diff, DirectoryGenerator-COCOON3-76.diff


 Remove jakarta-regexp dependency from all POMs: the only class using this is, 
 at the moment, DirectoryGenerator, in cocoon-optional.
 This class should be refactored to make use of java.util.regexp.* instead.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Created] (COCOON3-100) Make IncludeTransformer cacheable.

2012-05-20 Thread Javier Puerto (JIRA)
Javier Puerto created COCOON3-100:
-

 Summary: Make IncludeTransformer cacheable.
 Key: COCOON3-100
 URL: https://issues.apache.org/jira/browse/COCOON3-100
 Project: Cocoon 3
  Issue Type: Improvement
  Components: cocoon-pipeline, cocoon-sax
Affects Versions: 3.0.0-beta-1
Reporter: Javier Puerto


We need to implements CachingPipelineComponent. Like older Cocoon versions, we 
can ask for the SourceValidity of the implicated resources.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (COCOON3-100) Make IncludeTransformer cacheable.

2012-05-20 Thread Javier Puerto (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON3-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javier Puerto updated COCOON3-100:
--

Attachment: COCOON3-100.diff

Add CachedCacheKey class and URLCacheKey.
Move ObjectCacheKey from cocoon-optional.
Add caching support to IncludeTransformer.
Modify IncludeTransformer pipeline in cocoon-sample

 Make IncludeTransformer cacheable.
 --

 Key: COCOON3-100
 URL: https://issues.apache.org/jira/browse/COCOON3-100
 Project: Cocoon 3
  Issue Type: Improvement
  Components: cocoon-pipeline, cocoon-sax
Affects Versions: 3.0.0-beta-1
Reporter: Javier Puerto
 Attachments: COCOON3-100.diff


 We need to implements CachingPipelineComponent. Like older Cocoon versions, 
 we can ask for the SourceValidity of the implicated resources.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (COCOON3-100) Make IncludeTransformer cacheable.

2012-05-20 Thread Javier Puerto (JIRA)

[ 
https://issues.apache.org/jira/browse/COCOON3-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279749#comment-13279749
 ] 

Javier Puerto commented on COCOON3-100:
---

I've moved the ObjectCacheKey from cocoon-optional to cocoon-pipeline, please 
do a svn move instead.

The implementation could be better in performance because we need to open 
connections to the resources to get the Last-Modified header value but it's 
fine for file:// resources. Maybe an internal expires value?


 Make IncludeTransformer cacheable.
 --

 Key: COCOON3-100
 URL: https://issues.apache.org/jira/browse/COCOON3-100
 Project: Cocoon 3
  Issue Type: Improvement
  Components: cocoon-pipeline, cocoon-sax
Affects Versions: 3.0.0-beta-1
Reporter: Javier Puerto
 Attachments: COCOON3-100.diff


 We need to implements CachingPipelineComponent. Like older Cocoon versions, 
 we can ask for the SourceValidity of the implicated resources.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Commented] (COCOON3-30) The current implementation of the ParameterCacheKey actually breaks the caching

2012-05-20 Thread Javier Puerto (JIRA)

[ 
https://issues.apache.org/jira/browse/COCOON3-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13279753#comment-13279753
 ] 

Javier Puerto commented on COCOON3-30:
--

I've noticed while developing the patch for COCOON3-100 that ParameterCacheKey 
break the caching returning -1 for last modified value. This make caching by 
last modified useless because it's used for all pipelines.

 The current implementation of the ParameterCacheKey actually breaks the 
 caching
 ---

 Key: COCOON3-30
 URL: https://issues.apache.org/jira/browse/COCOON3-30
 Project: Cocoon 3
  Issue Type: Bug
  Components: cocoon-pipeline
Affects Versions: 3.0.0-alpha-1
Reporter: Steven Dolg
Assignee: Steven Dolg
Priority: Critical
 Fix For: 3.0.0-alpha-2

 Attachments: parametercachekey.patch


 The equals() and hashcode() implementations of the ParameterCacheKey do *not* 
 take the actual parameters into account.
 This makes it possible that different pipeline setups have the same cache key 
 and overwrite their cached results.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Updated] (COCOON3-100) Make IncludeTransformer cacheable.

2012-05-20 Thread Javier Puerto (JIRA)

 [ 
https://issues.apache.org/jira/browse/COCOON3-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Javier Puerto updated COCOON3-100:
--

Attachment: ResponseHeaderCollector.diff

Working on this patch I've unified how ResponseHeaderCollector retrieves the 
Long values.

 Make IncludeTransformer cacheable.
 --

 Key: COCOON3-100
 URL: https://issues.apache.org/jira/browse/COCOON3-100
 Project: Cocoon 3
  Issue Type: Improvement
  Components: cocoon-pipeline, cocoon-sax
Affects Versions: 3.0.0-beta-1
Reporter: Javier Puerto
 Attachments: COCOON3-100.diff, ResponseHeaderCollector.diff


 We need to implements CachingPipelineComponent. Like older Cocoon versions, 
 we can ask for the SourceValidity of the implicated resources.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira