On Tue, 29 May 2012 07:47:12 -0300, Magnus Kvalheim <mag...@kvalheim.dk>
wrote:
[2]CDI support
With Jee6 it's highly desirable to use cdi(jsr 299) for managing beans. I
dare to say in most cases spring can be avoided completely and what you
get is a app(s) with far less dependencies and configuration.
To top it off you even get conversational scope for free!
The module - https://github.com/magnuskvalheim/tapestry-cdi - could be
used as initial codebase for tapestry cdi.
Something I was thinking about Tapestry-IoC with CDI was the possibility
of configuring all services in Tapestry-IoC and then somehow pass them to
CDI, so CDI could handle transactions and stuff like that. We could also
provide injections from T-IoC to CDI. In this scenario, I was thinking of
having a different TapestryFilter implementation that sets a Registry
instance in the ServletContext that pulls services from CDI (T-IoC
indirectly) and not directly from T-IoC. This way, we can have the best of
both worlds (transactions and other stuff from CDI and the nice features
of T-IoC like distributed configuration, easy decoration of services,
etc). We probably would need
What do you think? I have no CDI experience, so I'm not sure what I'm
describing above is feasible. And this idea would be an option to what
you've done in tapestry-cdi, so people can choose what CDI integration
they want.
--
Thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
