Hide Forgot
Title: Update Application JNDI Namespace Names EJB 3.1 introduced a standardized global JNDI namespace and a series of related namespaces that map to the various scopes of a Java EE application. - the EJB 3.1 does introduce just that three namespaces where the session bean has to be bound to. The other namespaces could be defined in JavaEE spec and by particular vendor of app server. ...the three JNDI namespaces used for portable JNDI lookups are this should be reformulated as well. As the three namesapces are used for looking for the session beans
Modified the opening text in topic 4589 EJB 3.1 introduced a standardized global JNDI namespace and a series of related namespaces that map to the various scopes of a Java EE application. Portable EJB names only get bound to three of them: java:global, java:module, and java:app. Applications with EJBs that use JNDI must be changed to follow the new standardized JNDI namespace convention. Changes: Topic 4589 - 'Update Application JNDI Namespace Names' - rev 500566 Topic 19236 - 6.1.1 Migration Guide
The change is on-stage and ready for review (from Revision 1.0-65): http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBoss_Enterprise_Application_Platform/6.1.1/html/Migration_Guide/chap-Migrate_Your_Application.html#Update_Application_JNDI_Namespace_Names1