On 08/12/15 23:32, Mandy Chung wrote: > Good point. Existing code should use Annotation.annotationType() > instead of Annotation.getClass(). Annotation is an interface. Calling > annotation.getClass() will only return the implementation class that > may be encapsulated and not exported to the caller. This is not > specific to proxies. If the annotation were implemented with some > concrete implementation class that is not-exported to caller to use, > annotation.getClass().getMethod(…).invoke(…) will get IAE in that case. I did, which got me out of the jdk.proxy1 module issue, but then I was left with having to add a read to that annotation's module, which is only slightly better.
- Re: Is there really a jdk.proxy1 module? Stephane Epardaud
- Re: Is there really a jdk.proxy1 module... Peter Levart
- Re: Is there really a jdk.proxy1 m... Stephane Epardaud
- Re: Is there really a jdk.prox... Peter Levart
- Re: Is there really a jdk.prox... Stephane Epardaud
- Re: Is there really a jdk.prox... Mandy Chung
- Re: Is there really a jdk.prox... Stephane Epardaud
- Re: Is there really a jdk.prox... Peter Levart
- Re: Is there really a jdk.prox... Mandy Chung
- Re: Is there really a jdk.prox... Stephane Epardaud
- Re: Is there really a jdk.prox... Peter Levart
- Re: Is there really a jdk.proxy1 module... Remi Forax
- Re: Is there really a jdk.proxy1 module? Alan Bateman
- Re: Is there really a jdk.proxy1 module? Stephane Epardaud
