On Fri, Oct 24, 2008 at 3:16 PM, Thiago H. de Paula Figueiredo <[EMAIL PROTECTED]> wrote: > Em Fri, 24 Oct 2008 18:04:53 -0300, Howard Lewis Ship <[EMAIL PROTECTED]> > escreveu: > >> Current this is not possible; the Spring context is instantiated >> first, then the beans in it are "imported" as Tapestry IoC services. > > More one reason to build a tapestry-transaction package . . . If only I had > time to write it now . . . :( > >> We may see some improvements to this in 5.1. > > Nice! > >> Perhaps you could define an IoC version of a Spring bean whose >> implementation is the Spring bean itself, you could then decorate the >> IoC wrapper: > > But then I would need to inject a different service (same interface, > different id). It is a good solution, but not a complete one.
Yes, it is a stop-gap measure to address todays needs, but a full version would bring T5 IoC and Spring into parity, allowing T5 to decorate Spring beans, and injection of IoC services into Spring beans. Hopefully all that is possible. > > - > Thiago H. de Paula Figueiredo > Independent Java consultant, developer, and instructor > http://www.arsmachina.com.br/thiago > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
