On Thu, 05 May 2011 09:43:18 -0300, Magnus Kvalheim <mag...@kvalheim.dk>
wrote:
Hi Thiago - thanks for your answer,
Hi! You're welcome!
Think an implementation similar to tapestry-spring would the better
alternative of the two.
Agreed.
It's not completely clear to me what the difference is between an
ObjectProvider and ObjectCreator.
ObjectProvider is used inside Tapestry to provide injection when the
injected value is not a Tapestry-IoC service (bean).
I don't think ObjectCreator would be used in what you're trying to do, but
I never tried something like that and I can be completely wrong. :)
What do tapestry do with the beans after the're provided - are they
cached? (they seem to be cached as the provider is not called again)
And what about scopes? Again tapestry-spring give default(singleton)
scope to all, but can't see getServiceScope is called while debugging.
Tapestry-Spring, as stated in
http://tapestry.apache.org/integrating-with-spring-framework.html, just
handles singleton scopes correctly, so I guess they're cached.
Weld is bundled with glassfish so the BeanManager should be available
from jndi by the time tapestry starts up and loads the tapestry-cdi
module.
(In other environments it's possible to bootstrap manually - or use the
weld servlet listener, org.jboss.weld.environment.servlet.Listener)
The first option I'd try would be to have Tapestry to bootstrap Weld, as
it seems the easiest option.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
