Em Tue, 05 Jan 2010 14:42:48 -0200, Howard Lewis Ship <[email protected]>
escreveu:
I'm cautious about extending the ClassFactory/ClassFab APIs to support
this when my long term plan is to get away from Javassist entirely.
Maybe we should create a service that centralizes all the proxy creation
logic.
Further, I'm not sure how this will go together, because at the time
the IoC service proxy is created, the code does not necessarily know
the class that will be instantiated (especially if the service is
constructed using a build method, rather than via bind).
I was thinking about a best effort approach. Regarding building methods,
use whatever object it returns.
To be honest, I'd rather see an API to expose class and method
annotations on the core service implementation to advisors &
decorators.
It's not my ideal solution, but it's a good solution that solves almost
all the really important scenarios.
Any thoughts about it? I'm really eager to have this solved. :)
And even that will have issues for the perthread
lifecycle (where the core service implementation is itself a proxy).
If all proxies are created with the annotations of the proxied object, I
guess this isn't an issue.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, software architect and developer, 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]
