[jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1649) EJBs with <remote> element in ejb-jar.xml are not bound to JNDI when the jndi-name is overriden in jboss.xml

[jaikiran pai (JIRA)]

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

                 Key: EJBTHREE-1649
                 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1649
             Project: EJB 3.0
          Issue Type: Bug
          Components: proxy
    Affects Versions: 1.0.0-Beta10
         Environment: JBossAS-5.0 GA, RHEL5 Operating System, Sun Java 1.5
            Reporter: jaikiran pai
         Attachments: JNDIBindingTestCase.patch

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 at jpai] cd EJB3_TRUNK/testsuite
[jpai at jpai testsuite] mvn clean compiler:testCompile
[jpai at 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 at jpai testsuite]  ant -f build-test.xml one-test -Dtest=jndibinding




-- 
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