Incompatibility with Spring 3.1
-------------------------------
Key: TAP5-1797
URL: https://issues.apache.org/jira/browse/TAP5-1797
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-spring
Affects Versions: 5.3
Reporter: Martin Papy
Priority: Blocker
Tapestry fails starting with tapestry-spring and Spring 3.1 and
tapestry.use-external-spring-context = true. The same code works fine with
Spring 3.0.6
Apparently Spring 3.1 defines a new Service named 'environment' which is an ID
already used by Tapestry :
déc. 19, 2011 5:00:23 PM org.apache.catalina.core.StandardContext filterStart
Grave: Exception au démarrage du filtre TheOrcs
java.lang.RuntimeException: Service id 'environment' has already been defined
by
org.apache.tapestry5.services.TapestryModule.buildEnvironment(PerthreadManager)
(at TapestryModule.java:2560) and may not be redefined by
org.apache.tapestry5.ioc.internal.util.InternalUtils$10@17a19310. You should
rename one of the service builder methods.
at
org.apache.tapestry5.ioc.internal.RegistryImpl.<init>(RegistryImpl.java:180)
at
org.apache.tapestry5.ioc.RegistryBuilder.build(RegistryBuilder.java:177)
at
org.apache.tapestry5.internal.TapestryAppInitializer.createRegistry(TapestryAppInitializer.java:200)
at org.apache.tapestry5.TapestryFilter.init(TapestryFilter.java:109)
at
org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:295)
at
org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:422)
at
org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:115)
at
org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4001)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4651)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:546)
at
org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:637)
at
org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:563)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:498)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:321)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:785)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:445)
at
org.apache.catalina.core.StandardService.start(StandardService.java:519)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:581)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:322)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:450)
--
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
