users@glassfish.java.net

Re: How to find out the actual JNDI name of a EJB 2.1 Compatibility View?

From: Sahoo <Sahoo_at_Sun.COM>
Date: Fri, 30 May 2008 07:22:23 -0700

Is there any further info available in the EJB FAQ in glassfish site?

Sahoo

Markus Karg wrote:
> Thank you for that tips, but unfortunately it does not work.
>
> At runtime the ACC says: "javax.naming.NameNotFoundException: de.quipsy.sessions.escalationplanmanager.EscalationPlanManagerHome#null not found"
>
> In the generated sun-ejb-jar.xml I found exactly that name, but without trailing "#null". I don't know why ACC added that trailing "#null".
>
> In the JNDI Browser I found a subcontext "ejb", and inside it, exactly the same name (without trailing "#null").
>
> My application-client.xml is:
>
> <ejb-ref>
> <ejb-ref-name>ejb/EscalationPlanManager</ejb-ref-name>
> </ejb-ref>
>
> And my sun-application-client.xml ist:
>
> <ejb-ref>
> <ejb-ref-name>ejb/EscalationPlanManager</ejb-ref-name>
> <jndi-name>de.quipsy.sessions.escalationplanmanager.EscalationPlanManagerHome</jndi-name>
> </ejb-ref>
>
> What is my fault? Why doesn't that work? I am totally desparate.
>
> Thanks!
> Markus
>
> -----Original Message-----
> From: Sanjeeb.Sahoo_at_sun.com [mailto:Sanjeeb.Sahoo_at_sun.com] On Behalf Of Sahoo
> Sent: Freitag, 30. Mai 2008 14:54
> To: users_at_glassfish.dev.java.net
> Subject: Re: How to find out the actual JNDI name of a EJB 2.1 Compatibility View?
>
> You can browse the JNDI tree in the admin console. Or, you can see the
> information in sun-ejb-jar.xml file that GlassFish deployment backend
> generates. If you are looking for EJB inside foo.ear#ejb.jar, then look in:
>
> domains/domain1/generated/xml/j2ee-apps/foo/ejb_jar/META-INF/sun-ejb-jar.xml
>
> There you will the JNDI mapping information. If you care about
> portability across servers, then you specify the JNDI name for the EJB
> using @MappedName instead of relying on th default name that container
> generates.
>
> Thanks,
> Sahoo
>
> Markus Karg wrote:
>
>> In my application client running inside of ACC, I need to use new
>> InitialContext().lookup("java:comp/env/ejb/X") to lookup the EJB 2.1
>> compatibility view of my session bean. To make this work, I have to
>> specifiy a mapping from "ejb/X" to the actual JNDI name. But how to
>> find out the JNDI name that GlassFished by default applied? I did not
>> explicitely specify the JNDI name. What is the default?
>>
>>
>>
>> Thanks
>>
>> Markus
>>
>>
>>
>> QUIPSY QUALITY GmbH & Co. KG
>>
>> Ein Unternehmen der MES-Gruppe
>>
>> Stuttgarter Strasse 23
>>
>> D-75179 Pforzheim
>>
>> Tel: 07231-9189-52
>>
>> Fax: 07231-9189-59
>>
>> www.quipsy.de <http://www.quipsy.de>
>>
>> karg_at_quipsy.de <mailto:karg_at_quipsy.de>
>>
>> Registergericht Mannheim HRA 701214
>>
>> Geschäftsführer: Nils Schroeder
>>
>>
>>
>> Diese E-Mail enthält persönliche, vertrauliche und vor Weitergabe
>> geschützte Informationen und ist ausschließlich für den vorgesehenen
>> o.g. Empfänger (Adressaten) bestimmt. Falls Sie diese E-Mail
>> versehentlich erhalten haben und nicht der vorgesehene Empfänger sind,
>> bitten wir Sie, die E-Mail und deren Anhänge nicht aufzubewahren,
>> nicht zu vervielfältigen, nicht zu nutzen und nicht weiterzugeben.
>> Bitte informieren Sie uns als Absender über diesen Zustellungsfehler
>> und löschen Sie die E-Mail.
>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>