[
https://issues.apache.org/jira/browse/TAP5-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAP5-428.
-------------------------------------
Resolution: Fixed
Fix Version/s: 5.1.0.0
> It should be possible to use tapestry-spring in an environment where the
> Spring ApplicationContext is created externally (as was the case in Tapestry
> 5.0)
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-428
> URL: https://issues.apache.org/jira/browse/TAP5-428
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-spring
> Affects Versions: 5.1.0.0
> Reporter: Fernando
> Assignee: Howard M. Lewis Ship
> Priority: Blocker
> Fix For: 5.1.0.0
>
>
> Howard just added a feature trying to meld SpringContext and TapestryIoC. He
> thus added the requirement that Tapestry constructs the SpringContext. I
> want to request that a configuration is added to turn off this requirement,
> and have Tapestry use a normally constructed SpringContext.
> This will allow tapestry 5.1 to be fully backward compatible, etc etc..
> Some people might have special ways that they construct their SpringContext,
> and tapestry can't override that..
> Most people will not need to provide TapestryIoC services to spring, so
> breaking their code is harsh..
> (i would argue to have this feature disabled by default, and have people turn
> it on only when they understand the pros and cons!)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
