Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
3.2.1, 3.3
-
None
-
None
Description
ClientFactory tries to bind to java:comp/env/jbi/ClientFactory by default and this only appears to work when run as a standalone server. The java:comp/env naming context is read only according to the JEE spec so the ClientFactory can never bind to JNDI when deployed with JBoss deployer, WAR file, etc.
Attachments
Issue Links
- duplicates
-
SM-857 java:comp/env/ environment is read-only - Could not start ClientFactory javax.naming.NamingException
- Closed