On Wed, 08 Jan 2014 08:22:50 -0200, Nourredine K. <nourredin...@gmail.com>
wrote:
Hi,
Hi, Nourredine!
The idea is to make CDI and tapestry-ioc work together without
conflict and let you use existing projects based on CDI with Tapestry.
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. 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. ;)
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.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
