[ https://issues.apache.org/jira/browse/COCOON3-85?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175746#comment-13175746 ]
Francesco Chicchiriccò commented on COCOON3-85: ----------------------------------------------- What is your use case? I've just tried to replace <spring.version>3.0.7.RELEASE</spring.version> with <spring.version>3.1.0.RELEASE</spring.version> in parent/pom.xml, then launched it.sh and all went fine. > cocoon-spring-configurator doesn't work with Spring 3.1 > ------------------------------------------------------- > > Key: COCOON3-85 > URL: https://issues.apache.org/jira/browse/COCOON3-85 > 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 3.1. > 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira