[jboss-jira] [JBoss JIRA] (WFLY-13152) WFLYEJB0094: EJB 3.1 FR 5.4.2 MessageDrivenBean does not implement 1 interface nor specifies message listener interface

[Rhuan Rocha (Jira)]

    [ https://issues.redhat.com/browse/WFLY-13152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13982054#comment-13982054 ] 

Rhuan Rocha commented on WFLY-13152:
------------------------------------

 [~cfang] About the WAR, I have packaged the application via Maven and I have used the external jar in both.

{color:#DE350B}MessageDrivenComponentDescriptionFactory does check for the interface implemented by the super class of the bean class, but when the super class is not in the current module, the ClassInfo is not found in the current CompositeIndex:{color}

I agreed.  I have made tests in my local environment and I have noted it has many CompositeIndex instance and looks like it creates one instance per module. When the code search by interface information it is searching in a wrong instance. I have seen one of these instance has the correct information. I could not find the local in code that it select the CompositeIndex instance. 


> WFLYEJB0094: EJB 3.1 FR 5.4.2 MessageDrivenBean does not implement 1 interface nor specifies message listener interface 
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-13152
>                 URL: https://issues.redhat.com/browse/WFLY-13152
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB
>    Affects Versions: 17.0.1.Final
>            Reporter: Rhuan Rocha
>            Assignee: Cheng Fang
>            Priority: Major
>         Attachments: lib.zip, samplemdbear.zip
>
>
> The MDB does not works when it extends a superclass that comes from an external JAR and this super class implements the MessageListener. It generates this exception:
> {code:java}
> WFLYEJB0094: EJB 3.1 FR 5.4.2 MessageDrivenBean com.exemple.MyMDB does not implement 1 interface nor specifies message listener interface
> {code}
> These are what I have noted: 
> *   It only happens in a EAR project. In a WAR project it works fine.
> *   It only happens when the abstract class come from an external JAR
> *   If the sub class implements directly the MessageListener or if the messageListenerInterface is defined in the annotation it works fine.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)