Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Date: Sat, 19 Jan 2013 13:54:14 +0000 (UTC)
From: =?utf-8?Q?Francesco_Chicchiricc=C3=B2_=28JIRA=29?= <jira@apache.org>
To: dev@cocoon.apache.org
Message-ID: <JIRA.12536321.1324679436480.163848.1358603654837@arcas>
In-Reply-To: <JIRA.12536321.1324679436480@arcas>
References: <JIRA.12536321.1324679436480@arcas>
Subject: [jira] [Updated] (COCOON3-85) cocoon-spring-configurator doesn't
 work with latest (> 1.6.6) AspectJ's static optimizer
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/COCOON3-85?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Francesco Chicchiricc=C3=B2 updated COCOON3-85:
------------------------------------------

    Fix Version/s:     (was: 3.0.0-beta-1)
                   3.0.0
   =20
> cocoon-spring-configurator doesn't work with latest (> 1.6.6) AspectJ's s=
tatic 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-b=
eta-1
>            Reporter: Igor Malinin
>             Fix For: 3.0.0
>
>         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 Asp=
ectJ (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 do=
esn't work at all with Spring 3.1.
> Note that ServletContext is already in the Spring web-app context, althou=
gh with another name ('servletContext'). This is available starting from Sp=
ring 3.0. Making an alias 'javax.servlet.ServletContext' -> 'servletContext=
' solves problem partially, but still fails on XMLSitemapServlet initializa=
tion (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 ha=
ve as a dependency at leas 3.0 version of Spring Framework (for Java5 gener=
ics etc.)
> [1] http://old.nabble.com/Jetty-7---%22can%27t-determine-modifiers-of-mis=
sing-type-org.eclipse.jetty.webapp.WebAppContext$Context%22-error-td3231483=
9.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira