Remote JNDI lookup in Geronimo v2 m5

[mkv <va...@uk.ibm.com>]

Using Geronimo v2 m5 and deploying an EAR containing an EJB 2.1 bean now
works however the <ejb-name> value specified for a session bean in the
deployment plan is ignored and instead the bean appears to be given a JNDI
name along the lines of <bean jar name>/<bean name>. However doing a remote
lookup of <bean jar name>/<bean name> returns a JNDI subcontext not an EJB
Home object.

Question 1: Should the deployment of EJB 2.1 beans use the ejb-name value
from the deployment plan for compatibility with existing
applications/deployment plans?

Question 2: Given a lookup of <bean jar name>/<bean name> returns a JNDI
subcontext what should we lookup to obtain the EJB Home?


-- 
View this message in context: http://www.nabble.com/Remote-JNDI-lookup-in-Geronimo-v2-m5-tf3721854s134.html#a10414091
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.

Re: Remote JNDI lookup in Geronimo v2 m5

[mkv <va...@uk.ibm.com>]

At present you need to lookup <bean jar name>/<bean name>/<bean class name>

-- 
View this message in context: http://www.nabble.com/Remote-JNDI-lookup-in-Geronimo-v2-m5-tf3721854s134.html#a10740480
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.