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!)
|Field||Original Value||New Value|
|Assignee||Howard M. Lewis Ship [ hlship ]|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Summary||need a way to turn off tapestry constructing its own spring-context||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)|
|Component/s||tapestry-ioc [ 12312469 ]|
|Component/s||tapestry-spring [ 12312472 ]|
|Resolution||Fixed [ 1 ]|
|Status||In Progress [ 3 ]||Closed [ 6 ]|
|Fix Version/s||188.8.131.52 [ 12313428 ]|