Paul Sandoz wrote:
>
> BTW i verified the the case for Spring does as you point out.
>
In other words, it returns the proxy instead of the real object? Or are you
saying it works just fine?
Paul Sandoz wrote:
>
> I see your point. Is this not part of a larger issue in that CGLIB
> does not preserve annotations? Are we not attempting to work around a
> bug in CGLIB in this respect?
>
I don't think it's clear yet that this is something that can or should be
fixed in CGLIB (but yes, we all agree CGLIB is breaking compatibility).
1)
http://code.google.com/p/google-guice/issues/detail?id=201 indicates
copying annotations would involve a lot of work
2) I'm wondering if it's *always* safe to copy annotations down to the
subclass. Isn't it possible that 3rd-party tools might want to act on
annotations at runtime and they will mistakenly fire the same action once on
the proxy and once on the actual class? In other words, if some annotations
are "actionable" using a Annotation Processor at load-time then we have no
way of knowing which annotations are safe to copy and which are not.
Gili
--
View this message in context: http://n2.nabble.com/Simplifying-Jersey-life-cycle-and-IoC-integration-tp1367641p1573905.html
Sent from the Jersey mailing list archive at Nabble.com.