On Wed, 22 Dec 2010 14:17:34 -0200, Igor Drobiazko
<[email protected]> wrote:
Unfortunately there are some fundamental differences between JSR330 and
Tapestry IoC which make it impossible to provide a 100% portability. For
example JSR330 dictates that a downcast from an interface to the concrete
impl is posible:
MyService service = ...
MyServiceImpl impl = (MyServiceIml) service;
This won't work with the current implementation of proxies.
We could also provide Tapestry-IoC as an extension to CDI (JSR 299),
providing at least T-IoC services as beans and maybe even some advisers:
http://docs.jboss.org/weld/reference/latest/en-US/html/extend.html
--
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: [email protected]
For additional commands, e-mail: [email protected]
