[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] [Comment Edited] (COCOON-2347) Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version

2015-10-27 Thread Gabriel Gruber (JIRA)

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

Gabriel Gruber edited comment on COCOON-2347 at 10/27/15 1:04 PM:
--

The alternative of making the subproject cocoon-spring-configurator branch on a 
cocoon parent would be to set the spring-version locally, like this:

  
Cocoon Spring Configurator
2.2.1
../../../../../

1.7.0
1.0.7
4.2.2.RELEASE
  

  

  org.apache.cocoon
  cocoon-configuration-api
  1.0.4


  commons-io
  commons-io



  javax.servlet
  servlet-api
  provided


  org.springframework
  spring-core
  ${spring-version}


  org.springframework
  spring-context
  ${spring-version}


  org.springframework
  spring-beans
  ${spring-version}


  org.springframework
  spring-aop
  ${spring-version}


  org.springframework
  spring-web
  ${spring-version}




was (Author: ggruber):
The alternative of making the subproject cocoon-spring-configurator branch on a 
cocoon parent would be to set the spring-version locally, like this:

{code:xml}
  
Cocoon Spring Configurator
2.2.1
../../../../../

1.7.0
1.0.7
4.2.2.RELEASE
  

  

  org.apache.cocoon
  cocoon-configuration-api
  1.0.4


  commons-io
  commons-io



  javax.servlet
  servlet-api
  provided


  org.springframework
  spring-core
  ${spring-version}


  org.springframework
  spring-context
  ${spring-version}


  org.springframework
  spring-beans
  ${spring-version}


  org.springframework
  spring-aop
  ${spring-version}


  org.springframework
  spring-web
  ${spring-version}

{code}

> 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
> Attachments: AbstractElementParser.java.patch, 
> BeanMapElementParser.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-sitemap-impl
> - cocoon-servlet-service-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



--
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-27 Thread Gabriel Gruber (JIRA)

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

Gabriel Gruber edited comment on COCOON-2347 at 10/27/15 12:44 PM:
---

*CocoonSpringConfigurator* needs to be changed, as some methods of Spring 
BeanFactory have been extended with new signature variants and the usage of the 
cocoon project ist not precisely enough any longer.

See the attached patches for
- BeanMapElementParser.java
- WildCardBeanMap.java
- AbstractElementParser.java




was (Author: ggruber):
*Cocoon-Spring-Configurator* needs to be changed, as some methods of Spring 
BeanFactory have been extended with new signature variants and the usage of the 
cocoon project ist not precisely enough any longer.

See the attached patches for
- BeanMapElementParser.java
- WildCardBeanMap.java
- AbstractElementParser.java



> 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
> Attachments: AbstractElementParser.java.patch, 
> BeanMapElementParser.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-sitemap-impl
> - cocoon-servlet-service-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



--
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-27 Thread Gabriel Gruber (JIRA)

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

Gabriel Gruber edited comment on COCOON-2347 at 10/27/15 12:44 PM:
---

Cocoon-Spring-Configurator needs to be changed, as some methods of Spring 
BeanFactory have been extended with new signature variants and the usage of the 
cocoon project ist not precisely enough any longer.

See the attached patches for
- BeanMapElementParser.java
- WildCardBeanMap.java
- AbstractElementParser.java




was (Author: ggruber):
*CocoonSpringConfigurator* needs to be changed, as some methods of Spring 
BeanFactory have been extended with new signature variants and the usage of the 
cocoon project ist not precisely enough any longer.

See the attached patches for
- BeanMapElementParser.java
- WildCardBeanMap.java
- AbstractElementParser.java



> 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
> Attachments: AbstractElementParser.java.patch, 
> BeanMapElementParser.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-sitemap-impl
> - cocoon-servlet-service-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



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