[jboss-jira] [JBoss JIRA] (WFLY-3329) EJBs with same Java class name not intercepted by CDI interceptors

[Maxim Frolov (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966877#comment-12966877 ] 

Maxim Frolov edited comment on WFLY-3329 at 5/9/14 12:48 PM:
-------------------------------------------------------------

As far as I understand the Enterprise JavaBeans 3.1 spec does not require that all classes in an ear have unique java class names.

*§8.3.13 The Bean Provider’s View of the Deployment Descriptor:*, page 211:
??An ejb-name element for each entity bean. The ejb-name must be a valid Java identifier and must be *unique within* the ejb-name elements of the *ejb-jar* file.??

*§8.6.14 Entity Bean’s Deployment Descriptor:*, page 250:
??... The Bean Provider must specify unique names for entity beans which are defined in the ejb-jar file by using the ejb-name element.??

*§19.3 Application Assembler’s Responsibility,* page 533:
??... The Application Assembler uses the ejb-name of the referenced bean for the link. If there are multiple enterprise beans with the same ejb-name, the Application Assembler uses the path name specifying the location of the ejb-jar file that contains the referenced component. The path name is relative to the referencing ejb-jar/.war file. The Application Assembler appends the ejb-name of the referenced bean to the path name separated by #. This allows multiple beans with the same name to be uniquely identified??

*§19.5 Deployment Descriptor XML Schema,* page 538:
??The ejb-name element contains the name of an enterprise bean. The name must be unique within the ejb-jar or .war file.??


In my case EJB classes are deployed in *different JAR* files within an EAR.


was (Author: frolovmx):
As far as I understand the Enterprise JavaBeans 3.1 spec does not require that all classes in an ear have unique java class names.

*§8.3.13 The Bean Provider’s View of the Deployment Descriptor:*, page 211:
??An ejb-name element for each entity bean. The ejb-name must be a valid Java identifier and must be *unique within* the ejb-name elements of the *ejb-jar* file.??

*§8.6.14 Entity Bean’s Deployment Descriptor:*, page 250:
??... The Bean Provider must specify unique names for entity beans which are defined in the ejb-jar file by using the ejb-name element.??

*§19.3 Application Assembler’s Responsibility,* page 533:
??... The Application Assembler uses the ejb-name of the referenced bean for the link. If there are multiple enterprise beans with the same ejb-name, the Application Assembler uses the path name specifying the location of the ejb-jar file that contains the referenced component. The path name is relative to the referencing ejb-jar/.war file. The Application Assembler appends the ejb-name of the referenced bean to the path name separated by #. This allows multiple beans with the same name to be uniquely identified??

*§19.5 Deployment Descriptor XML Schema,* page 538:
??The ejb-name element contains the name of an enterprise bean. The name must be unique within the ejb-jar or .war file.??



> EJBs with same Java class name not intercepted by CDI interceptors
> ------------------------------------------------------------------
>
>                 Key: WFLY-3329
>                 URL: https://issues.jboss.org/browse/WFLY-3329
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: CDI / Weld
>    Affects Versions: JBoss AS7 7.1.1.Final, JBoss AS7 7.2.0.Final, 8.0.0.Final
>            Reporter: Maxim Frolov
>            Assignee: Stuart Douglas
>              Labels: ejb, ejb3.1, interceptor
>
> h3. Given
> Two or more EJBs with the same Java class name but from different Java deployments.
> h3. Problem
> Interceptor intercepts method calls to only one of the EJBs.
> An EJB to be intercepted seems to be chosen randomly after each redeployment.



--
This message was sent by Atlassian JIRA
(v6.2.3#6260)