You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Matt Raible (Updated) (JIRA)" <ji...@apache.org> on 2011/12/15 00:17:30 UTC
[jira] [Updated] (TAP5-1788) Service id 'environment' has already
been defined by org.apache.tapestry5.services.TapestryModule with Spring
3.1
[ https://issues.apache.org/jira/browse/TAP5-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Raible updated TAP5-1788:
------------------------------
Attachment: tapestry-spring-3.1-fix.patch
The attached patch solve this for me on trunk.
> Service id 'environment' has already been defined by org.apache.tapestry5.services.TapestryModule with Spring 3.1
> -----------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1788
> URL: https://issues.apache.org/jira/browse/TAP5-1788
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-spring
> Affects Versions: 5.2.4
> Reporter: Matt Raible
> Attachments: tapestry-spring-3.1-fix.patch
>
>
> After upgrading to Spring 3.1, started seeing the following error with Tapestry 5.2.4.
> java.lang.RuntimeException: Service id 'environment' has already been defined by org.apache.tapestry5.services.TapestryModule.buildEnvironment(PerthreadManager)
> More information at http://tapestry.1045711.n5.nabble.com/tapestry-5-2-4-and-spring-3-1M1-td4462226.html#a4742011
--
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