[jboss-jira] [JBoss JIRA] Created: (JBMETA-75) Interface-specific JNDI Name clashes with default JNDI name when mappedName is specified

[Andrew Lee Rubinger (JIRA)]

Interface-specific JNDI Name clashes with default JNDI name when mappedName is specified
----------------------------------------------------------------------------------------

                 Key: JBMETA-75
                 URL: http://jira.jboss.com/jira/browse/JBMETA-75
             Project: JBoss Metadata
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 1.0.0.Beta28
            Reporter: Andrew Lee Rubinger
         Assigned To: Andrew Lee Rubinger


Given the following specified mapped-name:

   "org.jboss.metadata.test.collision.MappedNameCollisionUnitTestCase-mapped-name"

JbossSessionBeanJndiNameResolver.resolveRemoteBusinessDefaultJndiName(smd) will return the same when using a BasicJndiBindingPolicy.

However, when requesting a target JNDI name for a business remote interface "org.jboss.Interface", the value received from:

JbossSessionBeanJndiNameResolver.resolveJndiName(smd, interfaceName) is :

   org.jboss.metadata.test.collision.MappedNameCollisionUnitTestCase-mapped-name/remote-org.jboss.Interface

Because the base name here is not a SubContext, there will be a binding error in JNDI.  This causes smoke test org.jboss.test.ejb3.test.SimpleSessionUnitTestCase and TCK tests to fail.



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira