The @Proxy annotation could, in principle, be useful, but I’m struggling to see how it’s supposed to be used in its current form. It feels like it would be more useful if it specified a list of proxied types, or perhaps if it were inverted so that you could exclude a type from the proxied types. Even then, I just struggle to see that anyone has a real need for this today. I think we can deprecate it for now, and if someone complains then we will get a chance to explore what their real use case is and how it’s best solved.
We’re using the annotation in an entity inheritance hierarchy to able to have final methods in the abstract class. Without the annotation we’re (still) getting an annoying warning at startup.
|
