-
Bug
-
Resolution: Done
-
Blocker
-
None
-
None
-
None
For determining the messagingType only directly implemented interfaces should be considered, not inherited.
java.lang.RuntimeException: Unable to choose messagingType interface for MDB CallbackBean from [interface javax.jms.MessageListener, interface javax.jms.MessageListener, interface com.sun.ts.tests.ejb30.common.callback.CallbackIF]
at org.jboss.ejb3.mdb.MDB.getMessagingType(MDB.java:77)
at org.jboss.ejb3.mdb.MDB.resolveBusinessInterfaces(MDB.java:116)
at org.jboss.ejb3.EJBContainer.instantiated(EJBContainer.java:1256)
at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:519)
... 72 more
- is duplicated by
-
EJBTHREE-1185 When the super class of an EJB3 MDB implements the same business interface a second time an "unable to determine messagingType interface for MDB" exception is thrown
- Resolved
- relates to
-
EJBTHREE-1122 Bean with multiple definitions of the same @Local or @Remote interface fails to deploy
- Closed