You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Tom Purcell (JIRA)" <ji...@apache.org> on 2007/02/23 22:52:05 UTC
[jira] Created: (GERONIMO-2884) JNDI Name Not Correct
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.
[jira] Updated: (GERONIMO-2884) JNDI Name Not Correct
Posted by "Matt Hogstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Hogstrom updated GERONIMO-2884:
------------------------------------
Fix Version/s: (was: 2.0)
2.0.x
> 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
> Assignee: David Blevins
> Fix For: 2.0.x
>
>
> 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.
[jira] Updated: (GERONIMO-2884) JNDI Name Not Correct
Posted by "Prasad Kashyap (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prasad Kashyap updated GERONIMO-2884:
-------------------------------------
Fix Version/s: (was: 2.0-M5)
2.0
> 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
>
>
> 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.
[jira] Assigned: (GERONIMO-2884) JNDI Name Not Correct
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods reassigned GERONIMO-2884:
--------------------------------------
Assignee: David Blevins
The nabble thread looked like you knew how to fix this and was going to get into 2.0-M3.....
> 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
> Assignee: David Blevins
> Fix For: 2.0
>
>
> 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.
[jira] Updated: (GERONIMO-2884) JNDI Name Not Correct
Posted by "Tom Purcell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Purcell updated GERONIMO-2884:
----------------------------------
Description:
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.
was:
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.
> 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.
[jira] Closed: (GERONIMO-2884) JNDI Name Not Correct
Posted by "David Blevins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Blevins closed GERONIMO-2884.
-----------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.0.x)
2.0.2
This appears to have been fixed in 2.0.2
> 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
> Assignee: David Blevins
> Fix For: 2.0.2
>
>
> 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.