cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francesco Chicchiriccò (Commented) (JIRA) <>
Subject [jira] [Commented] (COCOON3-85) cocoon-spring-configurator doesn't work with Spring 3.1
Date Mon, 26 Dec 2011 18:12:30 GMT


Francesco Chicchiriccò commented on COCOON3-85:

I have committed today some version updates in C3 sources (including Spring 3.1).

I have forked your GitHub project at git://

You can test my fork by:

# git clone  git://
# cd cocoon-springification
# mvn clean install
# cd webapp

At this point you can choose which JEE container to run with:

#  mvn -P cargo.jetty6x
# mvn -P cargo.tomcat7x
# mvn -P cargo.jetty7x
# mvn -P cargo.jetty8x

Without applying your patch, Jetty 6 and Tomcat 7 run fine, Jetty 7 and Jetty 8 fail with
stacktrace you reported above, so I think this is more a Jetty (7 and 8) issue than C3's.
> cocoon-spring-configurator doesn't work with Spring 3.1
> -------------------------------------------------------
>                 Key: COCOON3-85
>                 URL:
>             Project: Cocoon 3
>          Issue Type: Bug
>          Components: cocoon-servlet
>    Affects Versions: 3.0.0-beta-1
>            Reporter: Igor Malinin
>            Priority: Critical
>         Attachments: java.patch
> There are several issues that prevent Cocoon 3 to work with Spring 3.1
> One issue I reported already in mailing list when Jetty7 + recent AspectJ was failing,
not the same issue is deeper and ServletContextFactoryBean doesn't work at all with Spring
> Note that ServletContext is already in the Spring web-app context, although with another
name ('servletContext'). This is available starting from Spring 3.0. Making an alias 'javax.servlet.ServletContext'
-> 'servletContext' solves problem partially, but still fails on XMLSitemapServlet initialization
(as it uses static field in ServletContextFactoryBean).
> I will attach a patch (a little bit dirty, but not more than the current implementation).
But it assumes at least Spring 3.0.
> As Cocoon 3 project is moved to Java 1.6, it is probably also worth to have as a dependency
at leas 3.0 version of Spring Framework (for Java5 generics etc.)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message