Uploaded image for project: 'EJB 3.0'
  1. EJB 3.0
  2. EJBTHREE-1649

EJBs with <remote> element in ejb-jar.xml are not bound to JNDI when the jndi-name is overriden in jboss.xml

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Rejected
    • Affects Version/s: 1.0.0-Beta10
    • Fix Version/s: None
    • Component/s: proxy
    • Labels:
      None

      Description

      When a EJB contains the <remote> element in the ejb-jar.xml, the jndi-name specified in the jboss.xml is not used for binding. Furthermore, the JNDITree does not contain any bindings for this EJB. The EJB is just ignored from being bound to JNDI.

      Attached is the testcase to reproduce this on trunk. After applying this patch(testcase) to the trunk, follow the steps below to run the test:

      [jpai@jpai] cd EJB3_TRUNK/testsuite
      [jpai@jpai testsuite] mvn clean compiler:testCompile
      [jpai@jpai testsuite] ant -f build-test.xml jndibinding

      Start JBoss-5.0 GA server and wait for it to start. Set JBOSS_HOME to point to JBossAS-5.0 GA. Once the server is up, run

      [jpai@jpai testsuite] ant -f build-test.xml one-test -Dtest=jndibinding

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jaikiran Jaikiran Pai
                Reporter:
                jaikiran Jaikiran Pai
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: