On Fri, 28 Jun 2013 20:20:43 -0300, Howard Lewis Ship <hls...@gmail.com>
wrote:
As I remember it, I changed the API so that a search for an annotation
on a service will also check the service implementation ... so rather
than
"copy" the annotations (which is very, very problematic), the code looks
into two places. Take a peek at implementations of AnnotationProvider.
I'll take a look at it. This is a solution that only works inside
Tapestry-IoC. If you want to pass a T-IoC service for CDI, for example,
and have something that needs annotations in methods, transaction
handling, for example, this won't work.
I've never worked with bytecode instrumentation and ASM myself, so I don't
know what's problematic with copying annotations. Would you enlighten me?
:)
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
