cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Igor Malinin (Commented) (JIRA)" <>
Subject [jira] [Commented] (COCOON3-85) cocoon-spring-configurator doesn't work with Spring 3.1
Date Sat, 24 Dec 2011 17:06:30 GMT


Igor Malinin commented on COCOON3-85:

Hmm... Probably this is because I am using AspectJ 1.6.6 (newer versions break Cocoon on Jetty7+
because of ServletContextFactoryBean is not synthetic).

I'll try to get a stack trace for this and update my sample app so that you can reproduce
> 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