Hi Jarek,
Thanks for your reply. And I have decided to use application client to
continue my evaluation. I'll file a bug on the jndi-name issue.
Thanks,
Chris.
Jarek Gawor-2 wrote:
>
> Hi,
>
> Comments inline.
>
> On 7/2/07, Xiao-fei Song <[EMAIL PROTECTED]> wrote:
>>
>> Hi all,
>>
>> I am just working on geronimo v2 for a very simple ejb client application
>> but I got stuck on the jndi lookup part. I got 2 questions basically
>> because
>> my code runs well on geronimo 1.x:
>>
>> 1. jndi-name specified in openejb-jar.xml does not work. Is this being
>> ignored or a geronimo regression?
>
> Please open a bug and hopefully somebody will address it.
>
>> 2. when I try using deployment id as "MyEjbModule.jar/MySessionBean", the
>> look up returned subcontext instead of the home object, and I have a
>> ClassCastException while narrowing the object ref returned. The object's
>> class type is org.apache.openejb.client.JNDIContext instead of the home
>> interface.
>
> I believe, the default JNDI name in v2 is of the following format:
>
> {deploymentId}/{interfaceClass}
>
> where {deploymentId} is:
>
> {moduleId}/{ejbName}
>
> So you want to lookup something like:
> MyEjbModule.jar/MySessionBean/my.package.SessionRemote
>
> See
> http://svn.apache.org/viewvc/geronimo/server/trunk/testsuite/webservices-testsuite/jaxb-tests/jaxb-ejb/src/test/java/org/apache/geronimo/testsuite/testset/EJBJAXBTest.java?view=markup
> for an example.
>
> Hope this helps,
> Jarek
>
>
--
View this message in context:
http://www.nabble.com/jndi-name-and-sub-context-tf4011031s134.html#a11408619
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
