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

[JIRA]

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

Francesco Chicchiriccò commented on COCOON-2347:


I have created [1] as working branch for this work.

First question - possibly to [~jpuerto]: where shall we set the updated Spring 
version?
I'd say in [2], then re-publish to Nexus and set parent dependency to 
10-SNAPSHOT in [3]. Correct?

[1] 
https://svn.apache.org/repos/asf/cocoon/subprojects/cocoon-spring-configurator/branches/COCOON-2347/
[2] https://svn.apache.org/repos/asf/cocoon/trunk/parent/pom.xml
[3] 
https://svn.apache.org/repos/asf/cocoon/subprojects/cocoon-spring-configurator/branches/COCOON-2347/pom.xml

> 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)

Re: Cocoon 2.2 with Java 8 and Spring Framework 4.2?

[Francesco Chicchiriccò]

On 27/10/2015 13:37, Javier Puerto wrote:

Hi all,

@Gabriel, sounds very interesting and the update can bring some new 
energy to the project. :)


> Hum, is there anyone around with enough know-how about 2.2.?
Sorry Francesco, I was quite busy last three months but I will have 
some spare time in December so I could take a look into the changes.


Thanks Javier!
I have already set my very first question for you - see my comment in 
COCOON-2347.


Regards.

2015-10-27 13:25 GMT+01:00 Gabriel Gruber >:


Hello Folks,

nice to see the project still being alive :-)  I decided to make a
jira issue about our attempt to make cocoon 2.2 work with spring
framework 4.2.x.

https://issues.apache.org/jira/browse/COCOON-2347

I will append comments about progress etc. there and give you an
update on the mailing list as soon as something substantial could
be found out.

greets,
gabriel


> Francesco Chicchiriccò > wrote on 26.10.2015 15:37:00:

>> Hi Gabriel,
>> I do run actually few Cocoon instances in production, but that's 3.
>> 0.0(-beta-1-SNAPSHOT...). I used to run Cocoon 2.1.X as well.
>>
>> Unfortunately, I am not very confident with 2.2, but if you would
>> like to provide some patches against Spring Configurator [1] or
any
>> other component to bring them to latest Spring version, I would be
>> happy to review and handle your contribution(s).
>>
>> Please be sure to review our contribution docs[2].

>
> I am successfully running spring 4.0.6 with cocoon 2.2 in
production.
>
> I had to patch:
> - cocoon-pipeline-impl
> - cocoon-servlet-service-impl
> - cocoon-sitemap-impl
>
> anything higher in spring version fails. I do not recall the actual
> problems but they were deep in cocoon internals and I was unable to
> debug it properly.
>
> I have not been commiting those to cocoon repo as I have too little
> knowledge how these changes might affect cocoon overall. I could
> create a branch and commit my changes for someone more
experienced than me.
>
> WDYT?
>
> Hum, is there anyone around with enough know-how about 2.2.?


--
Francesco Chicchiriccò

Tirasa - Open Source Excellence
http://www.tirasa.net/

Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC
http://people.apache.org/~ilgrosso/

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

[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 commented on COCOON-2347:


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

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

[Gabriel Gruber (JIRA)]

Gabriel Gruber created COCOON-2347:
--

 Summary: 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


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.



--
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

[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

[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)

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

[Gabriel Gruber (JIRA)]

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

Gabriel Gruber updated COCOON-2347:
---
Attachment: WildcardBeanMap.java.patch
BeanMapElementParser.java.patch
AbstractElementParser.java.patch

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

[Gabriel Gruber (JIRA)]

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

Gabriel Gruber updated COCOON-2347:
---
Description: 
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-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

  was:
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


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

[Gabriel Gruber (JIRA)]

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

Gabriel Gruber updated COCOON-2347:
---
Description: 
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

  was:
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-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


> 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)

Fw: Cocoon 2.2 with Java 8 and Spring Framework 4.2?

[Gabriel Gruber]

Hello Folks,

nice to see the project still being alive :-)  I decided to make a jira 
issue about our attempt to make cocoon 2.2 work with spring framework 
4.2.x. 

https://issues.apache.org/jira/browse/COCOON-2347

I will append comments about progress etc. there and give you an update on 
the mailing list as soon as something substantial could be found out.

greets,
gabriel


> Francesco Chicchiriccò  wrote on 26.10.2015 
15:37:00:

>> Hi Gabriel,
>> I do run actually few Cocoon instances in production, but that's 3.
>> 0.0(-beta-1-SNAPSHOT...). I used to run Cocoon 2.1.X as well.
>> 
>> Unfortunately, I am not very confident with 2.2, but if you would 
>> like to provide some patches against Spring Configurator [1] or any 
>> other component to bring them to latest Spring version, I would be 
>> happy to review and handle your contribution(s).
>> 
>> Please be sure to review our contribution docs[2].

> 
> I am successfully running spring 4.0.6 with cocoon 2.2 in production. 
> 
> I had to patch:
> - cocoon-pipeline-impl
> - cocoon-servlet-service-impl
> - cocoon-sitemap-impl
> 
> anything higher in spring version fails. I do not recall the actual 
> problems but they were deep in cocoon internals and I was unable to 
> debug it properly.
> 
> I have not been commiting those to cocoon repo as I have too little 
> knowledge how these changes might affect cocoon overall. I could 
> create a branch and commit my changes for someone more experienced than 
me.
> 
> WDYT?
> 
> Hum, is there anyone around with enough know-how about 2.2.?
> -- 
> Francesco Chicchiriccò
> 
> Tirasa - Open Source Excellence
> http://www.tirasa.net/
> 
> Involved at The Apache Software Foundation:
> member, Syncope PMC chair, Cocoon PMC, Olingo PMC
> http://people.apache.org/~ilgrosso/

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

[JIRA]

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

Francesco Chicchiriccò updated COCOON-2347:
---
Description: 
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

  was:
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.


> 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
>
> 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)

Re: Fw: Cocoon 2.2 with Java 8 and Spring Framework 4.2?

[Javier Puerto]

Hi all,

@Gabriel, sounds very interesting and the update can bring some new energy
to the project. :)

> Hum, is there anyone around with enough know-how about 2.2.?
Sorry Francesco, I was quite busy last three months but I will have some
spare time in December so I could take a look into the changes.

Salu2.

2015-10-27 13:25 GMT+01:00 Gabriel Gruber :

> Hello Folks,
>
> nice to see the project still being alive :-)  I decided to make a jira
> issue about our attempt to make cocoon 2.2 work with spring framework
> 4.2.x.
>
> https://issues.apache.org/jira/browse/COCOON-2347
>
> I will append comments about progress etc. there and give you an update on
> the mailing list as soon as something substantial could be found out.
>
> greets,
> gabriel
>
>
> > Francesco Chicchiriccò  wrote on 26.10.2015
> 15:37:00:
>
> >> Hi Gabriel,
> >> I do run actually few Cocoon instances in production, but that's 3.
> >> 0.0(-beta-1-SNAPSHOT...). I used to run Cocoon 2.1.X as well.
> >>
> >> Unfortunately, I am not very confident with 2.2, but if you would
> >> like to provide some patches against Spring Configurator [1] or any
> >> other component to bring them to latest Spring version, I would be
> >> happy to review and handle your contribution(s).
> >>
> >> Please be sure to review our contribution docs[2].
>
> >
> > I am successfully running spring 4.0.6 with cocoon 2.2 in production.
> >
> > I had to patch:
> > - cocoon-pipeline-impl
> > - cocoon-servlet-service-impl
> > - cocoon-sitemap-impl
> >
> > anything higher in spring version fails. I do not recall the actual
> > problems but they were deep in cocoon internals and I was unable to
> > debug it properly.
> >
> > I have not been commiting those to cocoon repo as I have too little
> > knowledge how these changes might affect cocoon overall. I could
> > create a branch and commit my changes for someone more experienced than
> me.
> >
> > WDYT?
> >
> > Hum, is there anyone around with enough know-how about 2.2.?
> > --
> > Francesco Chicchiriccò
> >
> > Tirasa - Open Source Excellence
> > http://www.tirasa.net/
> >
> > Involved at The Apache Software Foundation:
> > member, Syncope PMC chair, Cocoon PMC, Olingo PMC
> > http://people.apache.org/~ilgrosso/
>

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

[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 commented on COCOON-2347:


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

[Gabriel Gruber (JIRA)]

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

Gabriel Gruber commented on COCOON-2347:


The following additional patches have to be applied:

cocoon-servlet-service-impl
- CallScope.java
- ServletScope.java
- ServletDecorator.java

cocoon-sitemap-impl:
- BridgeElementParser.java
- SitemapElementParser.java
- SourceResource.java
- AbstractTestCase.java
- MockRequestAttributes.java

cocoon-expression-api:
- ObjectModel.java
- MultiMap.java
- MultiValueMap.java

cocoon-expression-impl:
- ObjectModelImpl.java
- UnmodifieableMultiMap.java

cocoon-pipeline-impl:
- PipelineComponentScope.java
- PipelineComponentInfoInitializerDecorator.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-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



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

Re: Cocoon 2.2 with Java 8 and Spring Framework 4.2?

[Francesco Chicchiriccò]

On 27/10/2015 16:30, Gabriel Gruber wrote:

Hi Folks,

I was able to compile cocoon 2.2 with spring framework 4.2 and fix all 
the obvious problems like
- Using RootBeanDefinition.setScope() instead of 
RootBeanDefinition.setSingleton()
- finding the correct method calls after deprecated methods or 
constants have been removed.
- forking the commons-collections MultiMap and MultiValueMap classes 
into a util package of cooon-expression-language-api in order to make 
the interface compatible with Java 8 maps (conflict in remove() method!)
- implement missing methods in PipelineComponentScope, 
PipelineComponentInfoInitializerDecorator, CallScope, ServletScope, 
 MockRequestAttributes due to changes of Spring Superclasses
- implement missing method SourceResource.contentLength() due to 
change of Spring Superclass


Cool.
Which commandline are you using for building Cocoon 2.2? Bare "mvn clean 
install"?



However still a number of tests are failing like:
org.apache.cocoon.transformation.CIncludeTransformerTestCase.testCInclude1() 

org.apache.cocoon.transformation.CIncludeTransformerTestCase.testCInclude2() 


org.apache.cocoon.transformation.I18NTransformerTestCase.testI18n1()
org.apache.cocoon.transformation.I18NTransformerTestCase.testI18n2()
org.apache.cocoon.servletservice.AbsoluteServletConnectionTestCase.testURI() 

org.apache.cocoon.template.jxtg.JXTemplateGeneratorTestCase.testFormatDate() 

org.apache.cocoon.template.jxtg.JXTemplateGeneratorTestCase.testAttribute() 

org.apache.cocoon.template.jxtg.JXTemplateGeneratorTestCase.testElementSuccess() 



Ok, these needs of course to be reviewed and possibly adjusted.


Now I am able to start jetty with cocoon.


Even cooler.

When starting with Java 8 I get this error while accessing the start 
page (while the page is rendered correctly)


_org.apache.cocoon.ProcessingException_: Reader already set. Cannot 
set reader 'resource'|?at  - 
file:///C:/j2ee/open-sources/cocoon/cocoon-2.2-trunk-2015/blocks/cocoon-samples-style/cocoon-samples-style-default/target/classes/COB-INF/sitemap.xmap:63:44|?at 
 
- 
file:///C:/j2ee/open-sources/cocoon/cocoon-2.2-trunk-2015/blocks/cocoon-samples-style/cocoon-samples-style-default/target/classes/COB-INF/sitemap.xmap:62:35 

at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.setReader(_AbstractProcessingPipeline.java:298_) 

at 
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.setReader(_AbstractCachingProcessingPipeline.java:180_) 


at sun.reflect.NativeMethodAccessorImpl.invoke0(_Native Method_)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(_NativeMethodAccessorImpl.java:62_) 

at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(_DelegatingMethodAccessorImpl.java:43_) 


at java.lang.reflect.Method.invoke(_Method.java:497_)
at 
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(_PoolableProxyHandler.java:79_) 



The above exception only appears, if starting jetty with Java 8. When 
using a JRE7 it will not appear.


Ok, I would say to separate problems here, e.g. first let's make 
everything working with latest Spring + Java 7 and afterwards let's see 
how it works with Java 8. Agree?


After a bit more playing around with the (empty) samples page I get 
this error:


java.util.ConcurrentModificationException
at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901)
at java.util.ArrayList$Itr.next(ArrayList.java:851)
at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.setupPipeline(AbstractProcessingPipeline.java:360)
at 
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.setupPipeline(AbstractCachingProcessingPipeline.java:734)
at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.preparePipeline(AbstractProcessingPipeline.java:471)
at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process(AbstractProcessingPipeline.java:416)

at sun.reflect.GeneratedMethodAccessor58.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:497)
at 
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:79)

at com.sun.proxy.$Proxy17.process(Unknown Source)
at 
org.apache.cocoon.components.treeprocessor.sitemap.SerializeNode.invoke(SerializeNode.java:147)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
at 
org.apache.cocoon.components.treeprocessor.sitemap.SwitchSelectNode.invoke(SwitchSelectNode.java:88)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
at 
org.apache.cocoon.components.treeprocessor.sitemap.HandleErrorsNode.invoke(HandleErrorsNode.java:78)
at 

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

[Gabriel Gruber (JIRA)]

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

Gabriel Gruber updated COCOON-2347:
---
Description: 
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-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

  was:
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


> 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-servlet-service-impl
> - cocoon-sitemap-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] [Updated] (COCOON-2347) Make Cocoon 2.2 compatible with latest Spring Framework 4.2.x version

[Gabriel Gruber (JIRA)]

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

Gabriel Gruber updated COCOON-2347:
---
Description: 
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

  was:
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-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


> 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-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



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

Re: Cocoon 2.2 with Java 8 and Spring Framework 4.2?

[Gabriel Gruber]

Hi Folks,

I was able to compile cocoon 2.2 with spring framework 4.2 and fix all the 
obvious problems like
- Using RootBeanDefinition.setScope() instead of 
RootBeanDefinition.setSingleton()
- finding the correct method calls after deprecated methods or constants 
have been removed.
- forking the commons-collections MultiMap and MultiValueMap classes into 
a util package of cooon-expression-language-api in order to make the 
interface compatible with Java 8 maps (conflict in remove() method!)
- implement missing methods in PipelineComponentScope, 
PipelineComponentInfoInitializerDecorator, CallScope, ServletScope, 
MockRequestAttributes due to changes of Spring Superclasses
- implement missing method SourceResource.contentLength() due to change of 
Spring Superclass

However still a number of tests are failing like:
org.apache.cocoon.transformation.CIncludeTransformerTestCase.testCInclude1()
org.apache.cocoon.transformation.CIncludeTransformerTestCase.testCInclude2()
org.apache.cocoon.transformation.I18NTransformerTestCase.testI18n1()
org.apache.cocoon.transformation.I18NTransformerTestCase.testI18n2()
org.apache.cocoon.servletservice.AbsoluteServletConnectionTestCase.testURI()
org.apache.cocoon.template.jxtg.JXTemplateGeneratorTestCase.testFormatDate()
org.apache.cocoon.template.jxtg.JXTemplateGeneratorTestCase.testAttribute()
org.apache.cocoon.template.jxtg.JXTemplateGeneratorTestCase.testElementSuccess()


Now I am able to start jetty with cocoon.

When starting with Java 8 I get this error while accessing the start page 
(while the page is rendered correctly)

org.apache.cocoon.ProcessingException: Reader already set. Cannot set 
reader 'resource'|?at  - 
file:///C:/j2ee/open-sources/cocoon/cocoon-2.2-trunk-2015/blocks/cocoon-samples-style/cocoon-samples-style-default/target/classes/COB-INF/sitemap.xmap:63:44|?at
 
 - 
file:///C:/j2ee/open-sources/cocoon/cocoon-2.2-trunk-2015/blocks/cocoon-samples-style/cocoon-samples-style-default/target/classes/COB-INF/sitemap.xmap:62:35
at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.setReader(
AbstractProcessingPipeline.java:298)
at 
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.setReader(
AbstractCachingProcessingPipeline.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(
PoolableProxyHandler.java:79)

The above exception only appears, if starting jetty with Java 8. When 
using a JRE7 it will not appear.

After a bit more playing around with the (empty) samples page I get this 
error:

java.util.ConcurrentModificationException
 at 
java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901)
 at java.util.ArrayList$Itr.next(ArrayList.java:851)
 at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.setupPipeline(AbstractProcessingPipeline.java:360)
 at 
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.setupPipeline(AbstractCachingProcessingPipeline.java:734)
 at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.preparePipeline(AbstractProcessingPipeline.java:471)
 at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process(AbstractProcessingPipeline.java:416)
 at sun.reflect.GeneratedMethodAccessor58.invoke(Unknown 
Source)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:497)
 at 
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:79)
 at com.sun.proxy.$Proxy17.process(Unknown Source)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.SerializeNode.invoke(SerializeNode.java:147)
 at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.SwitchSelectNode.invoke(SwitchSelectNode.java:88)
 at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.HandleErrorsNode.invoke(HandleErrorsNode.java:78)
 at 
org.apache.cocoon.components.treeprocessor.sitemap.ErrorHandlerHelper.prepareErrorHandler(ErrorHandlerHelper.java:157)
 at 

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

[Gabriel Gruber (JIRA)]

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

Gabriel Gruber updated COCOON-2347:
---
Attachment: MultiValueMap.java
MultiMap.java

The files MultiMap.java and MultiValueMap.java have to be created in new 
package org.apache.cocoon.el.util inside project cocoon-expression-language-api

> 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, 
> 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



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

Re: Cocoon 2.2 with Java 8 and Spring Framework 4.2?

[Gabriel Gruber]

yes, I just use this:

mvn clean install -fn

Using following infrastructure on windows:
-  maven 3.3.3
- JDK 1.8.0_51

The -fn (fail never) switch gives me a nice summary at the end, which 
projects were successful and where there have been failures.

greets,
Gabriel






From:   Francesco Chicchiriccò 
To: dev@cocoon.apache.org
Date:   27.10.2015 17:42
Subject:Re: Cocoon 2.2 with Java 8 and Spring Framework 4.2?



On 27/10/2015 16:30, Gabriel Gruber wrote:
Hi Folks, 

I was able to compile cocoon 2.2 with spring framework 4.2 and fix all the 
obvious problems like 
- Using RootBeanDefinition.setScope() instead of 
RootBeanDefinition.setSingleton() 
- finding the correct method calls after deprecated methods or constants 
have been removed. 
- forking the commons-collections MultiMap and MultiValueMap classes into 
a util package of cooon-expression-language-api in order to make the 
interface compatible with Java 8 maps (conflict in remove() method!) 
- implement missing methods in PipelineComponentScope, 
PipelineComponentInfoInitializerDecorator, CallScope, ServletScope, 
 MockRequestAttributes due to changes of Spring Superclasses 
- implement missing method SourceResource.contentLength() due to change of 
Spring Superclass 

Cool.
Which commandline are you using for building Cocoon 2.2? Bare "mvn clean 
install"?

However still a number of tests are failing like: 
org.apache.cocoon.transformation.CIncludeTransformerTestCase.testCInclude1() 

org.apache.cocoon.transformation.CIncludeTransformerTestCase.testCInclude2() 

org.apache.cocoon.transformation.I18NTransformerTestCase.testI18n1() 
org.apache.cocoon.transformation.I18NTransformerTestCase.testI18n2() 
org.apache.cocoon.servletservice.AbsoluteServletConnectionTestCase.testURI() 

org.apache.cocoon.template.jxtg.JXTemplateGeneratorTestCase.testFormatDate() 

org.apache.cocoon.template.jxtg.JXTemplateGeneratorTestCase.testAttribute() 

org.apache.cocoon.template.jxtg.JXTemplateGeneratorTestCase.testElementSuccess()
 


Ok, these needs of course to be reviewed and possibly adjusted.

Now I am able to start jetty with cocoon. 

Even cooler.

When starting with Java 8 I get this error while accessing the start page 
(while the page is rendered correctly) 

org.apache.cocoon.ProcessingException: Reader already set. Cannot set 
reader 'resource'|?at  - 
file:///C:/j2ee/open-sources/cocoon/cocoon-2.2-trunk-2015/blocks/cocoon-samples-style/cocoon-samples-style-default/target/classes/COB-INF/sitemap.xmap:63:44|?at
 
 - 
file:///C:/j2ee/open-sources/cocoon/cocoon-2.2-trunk-2015/blocks/cocoon-samples-style/cocoon-samples-style-default/target/classes/COB-INF/sitemap.xmap:62:35
 

at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.setReader(
AbstractProcessingPipeline.java:298) 
at 
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.setReader(
AbstractCachingProcessingPipeline.java:180) 
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:62) 
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:43) 
at java.lang.reflect.Method.invoke(Method.java:497) 
at 
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(
PoolableProxyHandler.java:79) 

The above exception only appears, if starting jetty with Java 8. When 
using a JRE7 it will not appear. 

Ok, I would say to separate problems here, e.g. first let's make 
everything working with latest Spring + Java 7 and afterwards let's see 
how it works with Java 8. Agree?

After a bit more playing around with the (empty) samples page I get this 
error: 

java.util.ConcurrentModificationException
at 
java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901)
at java.util.ArrayList$Itr.next(ArrayList.java:851)
at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.setupPipeline(AbstractProcessingPipeline.java:360)
at 
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.setupPipeline(AbstractCachingProcessingPipeline.java:734)
at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.preparePipeline(AbstractProcessingPipeline.java:471)
at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process(AbstractProcessingPipeline.java:416)
at sun.reflect.GeneratedMethodAccessor58.invoke(Unknown 
Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:79)
at com.sun.proxy.$Proxy17.process(Unknown Source)
   

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

[Gabriel Gruber (JIRA)]

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

Gabriel Gruber updated COCOON-2347:
---
Attachment: PipelineComponentScope.java.patch
PipelineComponentInfoInitializerDecorator.java.patch
CallScope.java.patch
ServletScope.java.patch
ServletDecorator.java.patch
BridgeElementParser.java.patch
SitemapElementParser.java.patch
SourceResource.java.patch
AbstractTestCase.java.patch
MockRequestAttributes.java.patch

> 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, 
> AbstractTestCase.java.patch, BeanMapElementParser.java.patch, 
> BridgeElementParser.java.patch, CallScope.java.patch, 
> MockRequestAttributes.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



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

Re: Cocoon 2.2 with Java 8 and Spring Framework 4.2?

[Gabriel Gruber]

One thing I forgot: it would be really nice to centralize the spring 
version in a property within in the parent pom like this:

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

  
avalon-framework
avalon-framework
  
  
logkit
logkit
  

  
...


 
4.2.2.RELEASE

 
...



Then being able to easily switch between versions.

Mit freundlichen Grüssen / Best regards,

Mag. Gabriel Gruber
Geschäftsführung

Workflow EDV Gesm.b.H.
 
A-1030 Wien, Dannebergplatz 6/23
phone: +43 - 1 - 7188842 22
fax: +43 - 1 - 7188842 30
mobile: +43 - 676 - 3939435
mailto:gabriel.gru...@workflow.at
https://personalwolke.at
http://www.workflow.at
https://www.facebook.com/workflow.edv




From:   Gabriel Gruber 
To: dev@cocoon.apache.org
Date:   27.10.2015 17:53
Subject:Re: Cocoon 2.2 with Java 8 and Spring Framework 4.2?



yes, I just use this: 

mvn clean install -fn 

Using following infrastructure on windows: 
-  maven 3.3.3 
- JDK 1.8.0_51 

The -fn (fail never) switch gives me a nice summary at the end, which 
projects were successful and where there have been failures. 

greets, 
Gabriel 






From:Francesco Chicchiriccò  
To:dev@cocoon.apache.org 
Date:27.10.2015 17:42 
Subject:Re: Cocoon 2.2 with Java 8 and Spring Framework 4.2? 



On 27/10/2015 16:30, Gabriel Gruber wrote: 
Hi Folks, 

I was able to compile cocoon 2.2 with spring framework 4.2 and fix all the 
obvious problems like 
- Using RootBeanDefinition.setScope() instead of 
RootBeanDefinition.setSingleton() 
- finding the correct method calls after deprecated methods or constants 
have been removed. 
- forking the commons-collections MultiMap and MultiValueMap classes into 
a util package of cooon-expression-language-api in order to make the 
interface compatible with Java 8 maps (conflict in remove() method!) 
- implement missing methods in PipelineComponentScope, 
PipelineComponentInfoInitializerDecorator, CallScope, ServletScope, 
MockRequestAttributes due to changes of Spring Superclasses 
- implement missing method SourceResource.contentLength() due to change of 
Spring Superclass 

Cool.
Which commandline are you using for building Cocoon 2.2? Bare "mvn clean 
install"?

However still a number of tests are failing like: 
org.apache.cocoon.transformation.CIncludeTransformerTestCase.testCInclude1() 

org.apache.cocoon.transformation.CIncludeTransformerTestCase.testCInclude2() 

org.apache.cocoon.transformation.I18NTransformerTestCase.testI18n1() 
org.apache.cocoon.transformation.I18NTransformerTestCase.testI18n2() 
org.apache.cocoon.servletservice.AbsoluteServletConnectionTestCase.testURI() 

org.apache.cocoon.template.jxtg.JXTemplateGeneratorTestCase.testFormatDate() 

org.apache.cocoon.template.jxtg.JXTemplateGeneratorTestCase.testAttribute() 

org.apache.cocoon.template.jxtg.JXTemplateGeneratorTestCase.testElementSuccess()
 


Ok, these needs of course to be reviewed and possibly adjusted.

Now I am able to start jetty with cocoon. 

Even cooler.

When starting with Java 8 I get this error while accessing the start page 
(while the page is rendered correctly) 

org.apache.cocoon.ProcessingException: Reader already set. Cannot set 
reader 'resource'|?at  - 
file:///C:/j2ee/open-sources/cocoon/cocoon-2.2-trunk-2015/blocks/cocoon-samples-style/cocoon-samples-style-default/target/classes/COB-INF/sitemap.xmap:63:44|?at
 
 - 
file:///C:/j2ee/open-sources/cocoon/cocoon-2.2-trunk-2015/blocks/cocoon-samples-style/cocoon-samples-style-default/target/classes/COB-INF/sitemap.xmap:62:35
 

at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.setReader(
AbstractProcessingPipeline.java:298) 
at 
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.setReader(
AbstractCachingProcessingPipeline.java:180) 
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:62) 
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:43) 
at java.lang.reflect.Method.invoke(Method.java:497) 
at 
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(
PoolableProxyHandler.java:79) 

The above exception only appears, if starting jetty with Java 8. When 
using a JRE7 it will not appear. 

Ok, I would say to separate problems here, e.g. first let's make 
everything working with latest Spring + Java 7 and afterwards let's see 
how it works with Java 8. Agree?

After a bit more playing around with the (empty) samples page I get this 
error: 

java.util.ConcurrentModificationException
at 
java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901)
at 

Re: Cocoon 2.2 with Java 8 and Spring Framework 4.2?

[Javier Puerto]

2015-10-27 13:59 GMT+01:00 Francesco Chicchiriccò :

> On 27/10/2015 13:37, Javier Puerto wrote:
>
> Hi all,
>
> @Gabriel, sounds very interesting and the update can bring some new energy
> to the project. :)
>
> > Hum, is there anyone around with enough know-how about 2.2.?
> Sorry Francesco, I was quite busy last three months but I will have some
> spare time in December so I could take a look into the changes.
>
>
> Thanks Javier!
> I have already set my very first question for you - see my comment in
> COCOON-2347.
>

No problem. To reply the question I will need to check it with the code as
I don't remember ATM. I could take a look into the issue at Friday
afternoon or weekend.


>
> Regards.
>
>
> 2015-10-27 13:25 GMT+01:00 Gabriel Gruber :
>
>> Hello Folks,
>>
>> nice to see the project still being alive :-)  I decided to make a jira
>> issue about our attempt to make cocoon 2.2 work with spring framework
>> 4.2.x.
>>
>> https://issues.apache.org/jira/browse/COCOON-2347
>>
>> I will append comments about progress etc. there and give you an update
>> on the mailing list as soon as something substantial could be found out.
>>
>> greets,
>> gabriel
>>
>>
>> > Francesco Chicchiriccò < ilgro...@apache.org>
>> wrote on 26.10.2015 15:37:00:
>>
>> >> Hi Gabriel,
>> >> I do run actually few Cocoon instances in production, but that's 3.
>> >> 0.0(-beta-1-SNAPSHOT...). I used to run Cocoon 2.1.X as well.
>> >>
>> >> Unfortunately, I am not very confident with 2.2, but if you would
>> >> like to provide some patches against Spring Configurator [1] or any
>> >> other component to bring them to latest Spring version, I would be
>> >> happy to review and handle your contribution(s).
>> >>
>> >> Please be sure to review our contribution docs[2].
>>
>> >
>> > I am successfully running spring 4.0.6 with cocoon 2.2 in production.
>> >
>> > I had to patch:
>> > - cocoon-pipeline-impl
>> > - cocoon-servlet-service-impl
>> > - cocoon-sitemap-impl
>> >
>> > anything higher in spring version fails. I do not recall the actual
>> > problems but they were deep in cocoon internals and I was unable to
>> > debug it properly.
>> >
>> > I have not been commiting those to cocoon repo as I have too little
>> > knowledge how these changes might affect cocoon overall. I could
>> > create a branch and commit my changes for someone more experienced than
>> me.
>> >
>> > WDYT?
>> >
>> > Hum, is there anyone around with enough know-how about 2.2.?
>>
> --
> Francesco Chicchiriccò
>
> Tirasa - Open Source Excellencehttp://www.tirasa.net/
>
> Involved at The Apache Software Foundation:
> member, Syncope PMC chair, Cocoon PMC, Olingo 
> PMChttp://people.apache.org/~ilgrosso/
>
>

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

[Gabriel Gruber (JIRA)]

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

Gabriel Gruber updated COCOON-2347:
---
Attachment: ObjectModel.java.patch
ObjectModelImpl.java.patch

> 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, 
> AbstractTestCase.java.patch, BeanMapElementParser.java.patch, 
> BridgeElementParser.java.patch, CallScope.java.patch, 
> MockRequestAttributes.java.patch, 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



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