Just to wrap this up, in case anyone needs this information:
I "solved" the issue by making my own copy of the spring listener and
context loader and added logging instead of exception when this happens.
It turns out that Jetty calls the spring context loader twice, the second
time crashing. See
I also tried removing all links to tapestry 5, with the spring filter being
the only thing left in web.xml. Still same error in Jetty, still working in
Tomcat.
I'll stop posting about this here now, because this obviously has nothing to
do with Tapestry. It is probably due to something weird happe
Removed everything except the very essental stuff. Still getting the error.
Stripped down web.xml listed below:
http://java.sun.com/dtd/web-app_2_3.dtd";>
tapestry.app-package
no.dossier.moby.frontend.tapestry5
contextConfigLocation
/WEB-INF/backend-api.xml
http://java.sun.com/dtd/web-app_2_3.dtd";>
tapestry.app-package
no.dossier.moby.frontend.tapestry5
contextConfigLocation
/WEB-INF/backend-api.xml
tapestry5
org.apache.tapestry5.spring.TapestrySpringFilter
LinkLoginFilter
no.dossier.moby.fron
Let's see your web.xml.
On Sat, Feb 14, 2009 at 1:07 AM, Inge Solvoll wrote:
> Hi!
>
> I''m trying to get my T5 application up and running with Spring. I've placed
> the "kitchen sink" spring.jar in my WEB-INF/lib together with
> tapestry-spring.jar. I'm using T5.0.18.
>
> I'm testing this on Tom
