-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
-
None
Look in the code in EJB3 for anywhere we are binding anything into JNDI (search for bind). Catch any naming exception and wrap it with a new generic NamingException that
- sets the cause to be the thrown exception
- sets the exception message to be for example, "Could not bind EJB Foobars local interface", "Could not bind EntityManagerFactory with unitName XXXX to JNDI", etc...
- blocks
-
JBAS-2603 EJB3 update
- Closed