I think all of the CDI modules are basically a consumer layer so Tapestry pages/components/etc. can use CDI beans. Usually, the use case is that the rest of the company is using CDI, and the presentation layer (Tapestry) needs to use some of that functionality.
This may be off topic, but in all honesty, after working with both CDI and Tapestry-IOC for two years now, I would suggest phasing out Tapestry-IOC in favor of CDI. Tapestry-IOC was the biggest obstacle for me learning Tapestry IMHO. On May 15, 2013, at 1:19 PM, Thiago H de Paula Figueiredo wrote: > On Wed, 15 May 2013 10:35:36 -0300, Nourredine Nourredine > <nourredin...@gmail.com> wrote: > >> Hi, > > Hi! > >> Atos is proud to announce the first release of Tapestry-cdi, part of >> the got5[1] project. > > Yay! Thanks! > > 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. > > -- > Thiago H. de Paula Figueiredo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
