JNDI Name in EJB3

[Somesh Rathi]

My query is how and where to specify the JNDI Name while creating EJB3 ? I know in EJB3 , we dont have necessarily ejb-jar.xml.

I tried following:-
Defining global jndi name using mappedName attribute in @Stateless annonation. However when i'm running Test client ,I'm getting :-
javax.naming.NameNotFoundException: Unable to resolve 'CalculatorService'. exception


I'm created and deployed Stateless Session EJB3.0 Bean
Bean class is as follows

 
@Stateless (mappedName = "CalculatorService")
public class Calculator implements CalculatorRemote, CalculatorLocal {

    /**
     * Default constructor. 
     */
    public Calculator() {
      
    }
     public int add(int a, int b) {		
         return a+b;
    }
}

Test Class :- 

	public static void main(String[] args) {
		try {
			Hashtable<String, Object> ht = new Hashtable<String, Object>();
			ht.put(Context.INITIAL_CONTEXT_FACTORY,
					"weblogic.jndi.WLInitialContextFactory");
			ht.put(Context.PROVIDER_URL, "t3://localhost:7001");
			InitialContext ic = new InitialContext(ht);
			Calculator c = (Calculator) ic.lookup("CalculatorService");

			if (c instanceof Calculator) {

				int result = c.add(2, 3);
				System.out.println("Result" + result);
			}
		} catch (NamingException e) {
			// TODO Auto-generated catch block
			e.printStackTrace();
		}

	}
   

Many thanks in advance,
Somesh

[Ravi Kiran Va]

It should be someting like mappedName#

a proper google search under Oracle weblogic forums , will find you a solution .

[Manuel Alberto Quero]

Hi Somesh Rathi,

In EJB 3.0, JNDI names depend on the Application Server.
Weblogic builds global JNDI names for EJB remote references as follows:

mappedName\#interfacepackage.CalculatorRemote

interfacepackage: the package of CalculatorRemote

You can check this out by accessing Weblogic Admin Console (search for something like: Environment->Server->View JNDI Tree)


The name of EJB local references is defined in deployment descriptors (web.xml and ejb-jar.xml).

Anyway, if you do not want to use lookup explicitly, you could use the @EJB annotation.


Hope this helps,

Manuel