geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Purcell (JIRA)" <j...@apache.org>
Subject [jira] Created: (GERONIMO-2884) JNDI Name Not Correct
Date Fri, 23 Feb 2007 21:52:05 GMT
JNDI Name Not Correct
---------------------

                 Key: GERONIMO-2884
                 URL: https://issues.apache.org/jira/browse/GERONIMO-2884
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: OpenEJB
         Environment: Linux
            Reporter: Tom Purcell
             Fix For: 2.0-M2


I was asked to open this issue by David Blevins following this Nabble exchange: http://www.nabble.com/InitialContext-JNDI-Lookup-tf3273209s2756.html

The issue is that the JNDI entry under which an ejb's remote business interface is registered
is constructed as:
deploymentId/<BeanName>BussinessRemote

instead of
<ejb.jar file name>/<BeanName>BussinessRemote

this results in an entry that looks like this:
"geronimo-deploymentUtil5840.tmpdir/ConferenceCallSchedulerBeanBusinessRemote

The main problem with this is that the number part of the deployment id (5840 in the above)
will be different on each redeploy making it difficult for a client app to find.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message