[
https://issues.apache.org/jira/browse/TAP5-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246019#comment-13246019
]
Fernando Padilla commented on TAP5-1788:
----------------------------------------
I also have the same issue as Ralf. We need to go back to getting the
beanNames including ancestors/parents please.
are there any better solutions, can't we simply ignore the "environment" bean
from spring? Or can we just have Tapestry IoC prefer services defined from
Tapestry, before looking at spring based ones??
> 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
