[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

[Cheng Fang (Jira)]

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

Cheng Fang commented on WFLY-13152:
-----------------------------------

My proposal is to modify [MessageDrivenComponentDescriptionFactory|https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jboss/as/ejb3/deployment/processors/MessageDrivenComponentDescriptionFactory.java#L175] to search the super class {{ClassInfo}} in parent module, after failing to find it in the current module.  As we've already got a non-null {{superClassDotName}}, so the super class must exist somewhere.  Doing nothing after failing to find super class {{ClassInfo}} in current module is not right.  I'll try it out and send the PR if it works.

> 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)