[
https://issues.jboss.org/browse/WFLY-6293?page=com.atlassian.jira.plugin....
]
Stuart Douglas commented on WFLY-6293:
--------------------------------------
After thinking about this a bit more their are two complications that I can see:
1) There does not seem to be any requirement that bean names be alphanumeric, so it is
possible that applications may have bean names that contain special characters
2) Should these interceptors be considered class level interceptors or default
interceptors? I think they should probably be considered class level interceptors
WRT 1) I think we probably need some kind of setting to enable/disable this (possibly
overriding spec-descriptor-property-replacement, or adding another similar command).
<ejb-name> tag in <interceptor-binding> should support
regular expression usages
--------------------------------------------------------------------------------
Key: WFLY-6293
URL:
https://issues.jboss.org/browse/WFLY-6293
Project: WildFly
Issue Type: Feature Request
Components: EJB
Reporter: Wolf-Dieter Fink
Assignee: Stuart Douglas
From the ejb specification the only possibility is to use the full EJB name or the
wildcard "*".
* If the application is too large with many hundreds or thousand ejbs then it is complex
to define the interceptor individually for number of beans having a common name pattern.
The <ejb-name> element in <interceptor-binding> should support regular
expression usages. Like following via "ejb-jar.xml" or using
"jboss-ejb3.xml":
{code}
<interceptor-binding>
<ejb-name>Intercepted*Bean</ejb-name>
<interceptor-class>interceptors.InterceptorOne</interceptor-class>
</interceptor-binding>
<interceptor-binding>
<ejb-name>[AB]*Bean</ejb-name>
<interceptor-class>interceptors.InterceptorOne</interceptor-class>
</interceptor-binding>
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)