Problem solve
Get help with specific problems with your technologies, process and projects.
How can I communicate to EJB in another server?
Continue Reading This Article
Enjoy this article as well as all of our content, including E-Guides, news, tips and more.
Step 2 of 2:
One difference between accessing EJBs from local clients vs. remote clients is in the construction of the InitialContext for the bean. Remote clients typically obtain an InitialContext via an InitialContext factory, with server-specific credentials and URL, as in the following example:
Properties props = new Properties();
props.put(javax.naming.Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
props.put(javax.naming.Context.PROVIDER_URL, "t3://myhost:7001");
props.put(javax.naming.Context.SECURITY_PRINCIPAL, "jdoe");
props.put(javax.naming.Context.SECURITY_CREDENTIALS, "foobar");
javax.naming.Context context =
new javax.naming.InitialContext(props);
Object homeObject = context.lookup("java:comp/env/myejb");
MyEJBHome home = null;
if (usingIIOP == true)
{
home = (MyEJBHome)PortableRemoteObject.narrow(homeObject,
MyEJBHome.class);
}
else
{
home = (MyEJBHome)homeObject;
}
MyEJB myEJB = MyEJBHome.create();
Internal clients of an EJB, such as servlets, can simply create an InitialContext using the default constructor, as shown here:
javax.naming.Context context =
new javax.naming.InitialContext();
Object homeObject = context.lookup("java:comp/env/myejb");
MyEJBHome home = (MyEJBHome)homeObject;
MyEJB myEJB = MyEJBHome.create();
Dig Deeper on Topics Archive
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.
Meet all of our Application Architecture experts
Start the conversation
0 comments