[ https://issues.redhat.com/browse/WFLY-13152?page=com.atlassian.jira.plugi... ] Rhuan Rocha edited comment on WFLY-13152 at 2/25/20 11:38 AM: -------------------------------------------------------------- [~cfang] About the WAR, I have packaged the application via Maven and I have used the external jar in both. {color:#403294}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. was (Author: rhn-support-rhsilva): [~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. -- This message was sent by Atlassian Jira (v7.13.8#713008)