On Thu, 09 Jan 2014 13:58:45 -0200, Nourredine K. <nourredin...@gmail.com>
wrote:
Hi, Nourredine!
Hi Thiago!
Hi!
I saw that : ) thank you for fixing it
Thank everyone that contributed for the campaign and allowed me to have
time to work on the Tapestry codebase. :)
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] ?
https://github.com/got5/tapestry-cdi#using-cdi-beans-as-tapestry-services
I haven't checked myself, but I don't think that covers my dream scenario,
as the object is instantiated by CDI, not Tapestry, so distributed
configuration is lost.
BTW, I take your suggestion into account :)
Thank you very much. :)
--
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
