> Hi, Nourredine! Hi Thiago! > > I couldn't check tapestry-cdi (not even CDI itself yet, sigh), but I have a > dream scenario which I don't know whether tapestry-cdi supports it. If not, > consider it a suggestion. :) > > Tapestry-IoC has distributed configuration support, which is wonderful for > creating very flexible applications and libraries. In addition, it has an > incredibly easy to use AOP (advice and decoration) support.
Totally agree ! > On the other hand, it doesn't have complex transaction handling support like > Spring and > CDI do. I think it's not feasible to implement it in Tapestry-IoC. It would > demand developer time which we don't have. In addition, until some days ago, > the service proxies generated by T-IoC didn't have the annotations the > service implementation does, but the Month of Tapestry was able to fix that > limitation. ;) I saw that : ) thank you for fixing it > So my dream scenario is to create Tapestry-IoC services, somehow pass them > to CDI so we can use all the annotation-based CDI and EJB stuff like > transaction handling and RPC, and finally using these CDI-wrapped T-IoC > services in Tapestry or anywhere else just like they were vanilla T-IoC > services. Converting a CDI bean or an EJB into a tapestry service and making you thus benefit of the annotation-based CDI and transactionnal stuff inside a tapestry service is already possible[1]. The opposite is not at the moment, but could be worked around if you declare/contribute to your service by instantiating the class with CDI [1] ? BTW, I take your suggestion into account :) Note that CDI 1.1 (@Transactional annotation) will be part of jee7 [1] https://github.com/got5/tapestry-cdi#using-cdi-beans-as-tapestry-services --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
