Please, don't take my statements personally. I've been using these technologies for 2+ years. I grasp them fully. I stand by my opinion.
Now saying that, I am not saying Tapestry, or Tapestry-IOC sucks, I just feel Tapestry-IOC is unnecessary in the current technology landscape and presents a barrier to learning Tapestry. On May 15, 2013, at 3:57 PM, Kalle Korhonen wrote: > On Wed, May 15, 2013 at 12:42 PM, Lenny Primak <lpri...@hope.nyc.ny.us>wrote: > >> 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. >> > > It doesn't make it usual if that's the case in your company. > > 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. >> > > I just have to respond to that. I almost feel like you don't fully grasp > either technology. To me, the greatest thing in CDI is the SPI layer. It's > an inclusive technology that encourage the CDI providers to innovate on top > of the CDI spec. In regards to Tapestry-IOC are you really sure you'd like > to do away with things like distributed configuration? To me, that's one of > the greatest things in Tapestry-IOC. What we want is tighter integration > with CDI, not abandoning our IOC for some other implementation. > > Kalle > > > >> >> 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 >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
