You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by "Francesco Chicchiriccò (Updated JIRA)" <ji...@apache.org> on 2011/12/27 10:28:30 UTC
[jira] [Updated] (COCOON3-85) cocoon-spring-configurator doesn't
work with latest (> 1.6.6) AspectJ's static optimizer
[ https://issues.apache.org/jira/browse/COCOON3-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Chicchiriccò updated COCOON3-85:
------------------------------------------
Fix Version/s: 3.0.0-beta-1
Priority: Major (was: Critical)
Description:
As reported at first in mailing list [1], AspectJ's static optimizer was reviewed starting from 1.6.7 onward.
A temporary workaround for this is to force usage of version 1.6.6 of AspectJ (quite ancient right now).
At the moment Cocoon 3 is using latest Spring (3.1) and AspectJ (1.6.12) versions.
With Spring 3.1, this workaround is not enough any more.
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.)
[1] http://old.nabble.com/Jetty-7---%22can%27t-determine-modifiers-of-missing-type-org.eclipse.jetty.webapp.WebAppContext$Context%22-error-td32314839.html
was:
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.)
Affects Version/s: 3.0.0-alpha-1
3.0.0-alpha-2
3.0.0-alpha-3
Summary: cocoon-spring-configurator doesn't work with latest (> 1.6.6) AspectJ's static optimizer (was: cocoon-spring-configurator doesn't work with Spring 3.1)
> cocoon-spring-configurator doesn't work with latest (> 1.6.6) AspectJ's static optimizer
> ----------------------------------------------------------------------------------------
>
> 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-alpha-1, 3.0.0-alpha-2, 3.0.0-alpha-3, 3.0.0-beta-1
> Reporter: Igor Malinin
> Fix For: 3.0.0-beta-1
>
> Attachments: java.patch
>
>
> As reported at first in mailing list [1], AspectJ's static optimizer was reviewed starting from 1.6.7 onward.
> A temporary workaround for this is to force usage of version 1.6.6 of AspectJ (quite ancient right now).
> At the moment Cocoon 3 is using latest Spring (3.1) and AspectJ (1.6.12) versions.
> With Spring 3.1, this workaround is not enough any more.
> 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.)
> [1] http://old.nabble.com/Jetty-7---%22can%27t-determine-modifiers-of-missing-type-org.eclipse.jetty.webapp.WebAppContext$Context%22-error-td32314839.html
--
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