Setting JNDI name for EJB 3.0 bean from weblogic-ejb-jar.xml (Doc ID 1306833.1)

Last updated on NOVEMBER 05, 2016

Applies to:

Oracle Weblogic Server - Version: 10.3 and later   [Release: and later ]
Information in this document applies to any platform.

Symptoms

The environment was:

- WLS 10.3.4
- Spring application
- Win XP

- When trying to set the JNDI name for a EJB 3 bean from weblogic-ejb-jar.xml:

<weblogic-ejb-jar xmlns="http://xmlns.oracle.com/weblogic/weblogic-ejb-jar" version="1.0">

<weblogic-enterprise-bean>
 <ejb-name>HelloService</ejb-name>
 <jndi-name>short.HelloService</jndi-name>
 </weblogic-enterprise-bean>
</weblogic-ejb-jar>

It is correctly handled by WebLogic Server:

 In the log file, it can be seen:
####<4  mars 2011 17 h 59 CET> <Info> <EJB> <ovaladie-fr> <AdminServer> 
<[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'>
<> <> <> <1299257940687>
<BEA-010009> <EJB Deployed EJB with JNDI name short.HelloService.>

Here the problem deals with the JNDI tree: there's NO corresponding JNDI entry "short.HelloService", instead only available is: "ear-1ejb-1_0_jarHelloService_Home"

Note: The JNDI name "ear-1ejb-1_0_jarHelloService_Home" is the concatenation of:
- the EAR application name is "ear-1",
- the EJB embedded with this EAR is "ejb-1.0"
- the remote home name of this EJB is "HelloService"


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms