[
https://issues.apache.org/jira/browse/TAP5-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219871#comment-13219871
]
Ralf Edmund Stranzenbach commented on TAP5-1788:
------------------------------------------------
This solution has an undesired side effect. It prevents me from using a
centralized spring context that is associated as a "parent context" to the
"application.xml" loaded by the tapestry-spring filter.
Only the few beans assigned to the web-app specific part of the spring
configuration are therefore visible to the tapestry injector. The main part of
my applications infrastructure became invisible to tapestry.
A better solution would be to either assign an implicit "namespace" to spring
beans in case they duplicate a service name already used in tapestry. This
would enable the use of parent spring context while preventing the duplicate
"Environment" service.
> 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
> Assignee: Igor Drobiazko
> Fix For: 5.3.2, 5.4
>
> 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
