-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
AS 4.2.2.GA
-
None
-
None
The class org.jboss.ejb3.mdb.MDB.getMessagingType() throws a RuntimeException("unable to determine messagingType interface for MDB") when a s super class of an MDB implements the business interface.
To fix this bug the org.jboss.ejb3.ProxyFactoryHelper.getBusinessInterfaces(clazz) method could use internally a Set instead of a list, this would be preferred and least surprising semantic in my opinion.
Caused by: java.lang.RuntimeException: unable to determine messagingType interface for MDB
at org.jboss.ejb3.mdb.MDB.getMessagingType(MDB.java:88)
at org.jboss.ejb3.interceptor.EJB3InterceptorsFactory.getBusinessInterfaces(EJB3InterceptorsFactory.java:167)
at org.jboss.ejb3.interceptor.EJB3InterceptorsFactory.isBusinessMethod(EJB3InterceptorsFactory.java:122)
at org.jboss.ejb3.interceptor.EJB3InterceptorsFactory.createPerJoinpoint(EJB3InterceptorsFactory.java:98)
... 154 more
- duplicates
-
EJBTHREE-1123 Determining the messagingType of a MDB considers too many interfaces
- Closed
- relates to
-
EJBTHREE-1062 Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work
- Resolved