Uploaded image for project: 'JBoss Metadata'
  1. JBoss Metadata
  2. JBMETA-75

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 1.0.0.Beta29
    • 1.0.0.Beta28
    • None
    • None

      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.

              arubinge@redhat.com Andrew Rubinger (Inactive)
              arubinge@redhat.com Andrew Rubinger (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: