-
Bug
-
Resolution: Done
-
Blocker
-
4.3.0.GA_CP01, 4.2.0.GA_CP03
-
None
-
EAP 4.3.0
-
Release Notes, Compatibility/Configuration
-
Workaround Exists
-
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.
- relates to
-
JBAS-53 Rewrite of ENC for Web, EJB 2.1, and EJB 3.0
-
- Closed
-