I've have what I hope is a really easy question to answer. I have a number
of Session beans deployed to Orion (1.4.4 level), and everything works great
when communicating from an application client (JSPs and servlets running
Apache Tomcat) to the Orion server. Now I want to add some EJB to EJB
communication, with one EJB obtaining the home and remote interfaces of
another EJB and executing methods on that remote interface.
When I attempt to lookup my bean using the JNDI context, I get an exception
being thrown that says that it can't find the JNDI lookup name in the
Application Client. I assume that Orion is not finding the
application_client.xml file within its own environment. What are others
doing to rectify this situation? I assume that EJB to EJB communication is
**very common**, as most people are using Session bean fascades around their
Entity beans. An example of this sort of functionality and the steps needed
to configure it should be available through Orion or orionsupport.com, but I
could not find anything.
Thanks in advance.
-- chris bartling --
