+1. Webservices are another example. I already had a look at that problem but I'm too unfamiliar
with the respective code...
Uli
On 20.05.2010 04:44, Thiago H. de Paula Figueiredo wrote:
On Wed, 19 May 2010 23:19:35 -0300, Howard Lewis Ship <[email protected]>
wrote:
The first transition is to move away from Javassist to a simpler, more
stable (more JDK 1.6 compatible) approach to dynamic class generation
and runtime bytecode transformation. This has been reflected in the
new ClassTransformation APIs. However, there is more yet to do,
including a similar update of the ClassFactory/ClassFab APIs. Will
that last part make it into 5.2?
Regarding this interfaces and their implementations, what I really miss
in Tapestry-IoC is the annotations in service implementations methods
being added to ther proxy counterparts. This obliges us to add
annotations to service definitions (interfaces) so they can be
recognized through reflection, and not always we have the possibility of
doing this change. This also prevents services built in Tapestry-IoC to
be used in other frameworks that process anotations. CDI (JSR 330) is
one of them.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
