Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-933

EJB2 failing to deploy when packaged with EJB3 Service Bean

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • 4.3.0.GA_CP01, 4.2.0.GA_CP03
    • EJB
    • None
    • EAP 4.3.0

    • Release Notes, Compatibility/Configuration
    • Workaround Exists
    • Hide

      Deploy EJB2 and EJB3 jars in separate EAR's.

      Show
      Deploy EJB2 and EJB3 jars in separate EAR's.

      If you perform a lookup that invokes the SimpleMultiplexer when starting a Service Bean (e.g. new InitialContext().lookup("java:comp/...") within start() method ),
      it will create a Naming context (when it looks up comp.original using the ENCFactory) and associate it with the applications class loader.

      If an EJB2 is deployed after this (within the same application) it will bind the beans environment with the Naming Context associated with the applications UnifiedClassLoader.

      Subsequent deployments of EJB2 beans will also do this and fail.

        1. JBPAPP-933.patch
          26 kB
          Carlo de Wolf
        2. testContext.ear
          5 kB
          David Stephan
        3. testContext-src.tar.gz
          3 kB
          David Stephan

              jaikiran Jaikiran Pai (Inactive)
              rhn-support-dstephan David Stephan (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: