On Wed, 15 May 2013 14:19:11 -0300, Thiago H de Paula Figueiredo <thiag...@gmail.com> wrote:
One (maybe stupid) question: does it allow Tapestry services to be provided as CDI beans, so they can have transaction handling or other CDI-provided stuff, and still be injectable through Tapestry-IoC? That would be the best of two worlds: Tapestry-IoC's easy declaration of services with distributed configuration plus CDI-provided goodness.
What about having Tapestry-IoC as a CDI portable extension which registers T-IoC services as CDI beans? This way, we can still have the best of two worlds without Tapestry-IoC implementing CDI and with way less work. -- Thiago H. de Paula Figueiredo --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
