Yes please, breaking the original spring integration is a huge blocker.
The old spring integration ( exposing spring beans into Tapestry IoC )
was very good, and necessary. If you wanted to bring a completely
different way to integrate with spring, I would have voted for a second
package, since they seem totally different.. spring-to-tapestry, versus
tapestry-to-spring. They solve two totally different things.. Could
have called them tapestry-fromSpring and the new tapestry-toSpring
packages..
:) :)
On 12/31/08 2:07 PM, Howard Lewis Ship wrote:
I supposed I could add a backwards compatibility mode; I was hoping to
escape exposing the beans as services since it is not a very good fit,
especially w.r.t. bean scope vs. service scope.
On Tue, Dec 30, 2008 at 3:51 PM, Fernando Padilla<[email protected]> wrote:
So.. thank you very much for taking care of a way to turn off the new
spring-context feature!! :)
Now, it looks like the new work has disabled the original feature of
exposing all of the spring beans through Tapestry IoC..
https://issues.apache.org/jira/browse/TAP5-431
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
