[
https://issues.jboss.org/browse/CDI-468?page=com.atlassian.jira.plugin.sy...
]
Martin Kouba commented on CDI-468:
----------------------------------
Looks like a good idea. We should probably expose the set of all method/constructor
interceptor bindings:
{code}
Collection<Annotation> getInterceptorBindings();
{code}
And this set could be empty if there are no bindings declared and only interceptors using
the {{@Interceptors}} annotation are associated.
Anyway, if we conclude that this is useful and doable we should file a new interceptor
spec issue.
Extend javax.interceptor.InvocationContext
------------------------------------------
Key: CDI-468
URL:
https://issues.jboss.org/browse/CDI-468
Project: CDI Specification Issues
Issue Type: Feature Request
Reporter: Arne Limburg
Currently there is no easy way to obtain the interceptor binding annotation for an
interceptor call. The interceptor binding annotation is needed to access @Nonbinding
attributes and behave accordingly.
I propose to extend the javax.interceptor.InvocationContext interface with a method
public Annotation getInterceptorBinding() or
public <A extends Annotation> A getInterceptorBinding(Class<A> type)
The @AroundInvoke method of CDI Interceptors may use this extended interface as parameter
instead of the original one to obtain the interceptor binding annotation.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)