Uploaded image for project: 'EJB 3.0'
  1. EJB 3.0
  2. 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

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Duplicate Issue
    • Affects Version/s: AS 4.2.2.GA
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      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

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  wolfc Carlo de Wolf
                  Reporter:
                  wv-javacoder Roland Räz
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: