[cdi-dev] [Vote] for CDI-527 / PR 271 allow proxying of classes with non-private final methods
jens.schumann at openknowledge.de
Mon Feb 15 03:25:34 EST 2016
Von: <cdi-dev-bounces at lists.jboss.org<mailto:cdi-dev-bounces at lists.jboss.org>> on behalf of Romain Manni-Bucau <rmannibucau at gmail.com<mailto:rmannibucau at gmail.com>>
Datum: Saturday 13 February 2016 23:30
An: "John D. Ament" <john.d.ament at gmail.com<mailto:john.d.ament at gmail.com>>
Cc: CDI-Dev <cdi-dev at lists.jboss.org<mailto:cdi-dev at lists.jboss.org>>
Betreff: Re: [cdi-dev] [Vote] for CDI-527 / PR 271 allow proxying of classes with non-private final methods
The gotcha that I still see is around interceptor bindings. They need to be explicitly disallowed on final methods, and big ole warning put in when you have interceptors on classes with final methods.
In my experience legacy (framework) code tends to have protected final methods, so the problems might be less dangerous than they appear first place (regarding interceptors).
I would just warn that a non-proxyable class is proxied, and certain problems arise by doing so. You can name the problems, sure. But I think it is ok to say (in bold): Yes, we do what you want. But live with the consequences.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cdi-dev