When mappedName is equal to deploymentScopeBaseName, JNDI Name Collisions occur ------------------------------------------------------------------------------- Key: JBMETA-83 URL: https://jira.jboss.org/jira/browse/JBMETA-83 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.0.Beta31 Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Assuming an EJB with: mappedName = myBase deploymentScopeBaseName = myBase Then the Default Remote Business Interface will be: "myBase" And the base upon which JNDI Names are built will be: "myBase/ejbname/" Because the JNDI Name base starts with the mappedName, which is bound, a subcontext cannot be created and therefore presents a JNDI Collision. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira