[
https://issues.jboss.org/browse/WFLY-4200?page=com.atlassian.jira.plugin....
]
Eduardo Silva commented on WFLY-4200:
-------------------------------------
I believe that the problem is because
AnnotatedEJBComponentDescriptionDeploymentUnitProcessor executes in the parse phase:
Phase.PARSE,Phase.PARSE_CREATE_COMPONENT_DESCRIPTIONS
Since the dependencies will be resolved at Phase.DEPENDENCIES, your build will not work.
Regarding WFLY, my suggestion is not throw the
EjbLogger.ROOT_LOGGER.mdbDoesNotImplementNorSpecifyMessageListener(beanClass) only bring
up some flag that the required interfaces were not yet resolved, some attachment could be
useful, just to retain the super class name. When the dependencies were solved, the class
will be present on the class index and the test against the annotation should be performed
again. Since that work will be done twice, to verify the required interfaces, this
requires some experts advice.
WAR MDB cannot obtain superclass on module classpath
----------------------------------------------------
Key: WFLY-4200
URL:
https://issues.jboss.org/browse/WFLY-4200
Project: WildFly
Issue Type: Bug
Components: Class Loading, EJB
Affects Versions: 8.2.0.Final
Reporter: John Mazzitelli
Priority: Minor
Attachments: mdb-test.zip
see the forum post for details:
https://developer.jboss.org/message/914355
but suffice it to say this is similar to
https://issues.jboss.org/browse/AS7-2638 which
appears to have come back again.
In my WAR, I have an MDB which extends a class (in which that superclass implements
MessageListener) and that superclass is in a module that my WAR depends on; the MDB fails
to deploy. I have to explicitly add an annotation attribute to workaround the problem.
Again, see the forum for the very easy steps to replicate with a small zip file that
contains the replication code.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)