Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Date: Mon, 26 Dec 2011 18:12:30 +0000 (UTC)
From: =?utf-8?Q?Francesco_Chicchiricc=C3=B2_=28Commented=29_=28JIRA=29?=
 <jira@apache.org>
To: dev@cocoon.apache.org
Message-ID: 
 <1790154391.45437.1324923150706.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1597314301.43325.1324679551251.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (COCOON3-85) cocoon-spring-configurator doesn't
 work with Spring 3.1
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.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1317=
5984#comment-13175984 ]=20

Francesco Chicchiricc=C3=B2 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://github.com/ilgrosso/cocoon-sprin=
gification.git

You can test my fork by:

# git clone  git://github.com/ilgrosso/cocoon-springification.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
or
# mvn -P cargo.tomcat7x
or
# mvn -P cargo.jetty7x
or
# mvn -P cargo.jetty8x

Without applying your patch, Jetty 6 and Tomcat 7 run fine, Jetty 7 and Jet=
ty 8 fail with stacktrace you reported above, so I think this is more a Jet=
ty (7 and 8) issue than C3's.
               =20
> 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 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.)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira