Hi!
You need to specify reference to EJB, that you using from another EJB in
ejb-jar.xml:
Something like this:
<session>
<display-name>MySession1</display-name>
<ejb-name>MySession1</ejb-name>
<home>MySession1Home</home>
<remote>MySession1</remote>
<ejb-class>MySession1EJB</ejb-class>
...<!-- may be reference to datasource -->...
<ejb-ref>
<ejb-ref-name>ejb/MySession2</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<home>MySession2Home</home>
<remote>MySession2</remote>
<ejb-link>MySession2</ejb-link>
</ejb-ref>
</session>
<session>
<display-name>MySession2</display-name>
<ejb-name>MySession2</ejb-name>
<home>MySession2Home</home>
<remote>MySession2</remote>
<ejb-class>MySession2EJB</ejb-class>
...<!-- may be reference to datasource -->...
</session>
In code of MySession1 you can look up "java:comp/env/MySession2" and obtain
remote-interface of MySession2 EJB.
I hope you understand me.
Daniel Degtyarev.
----- Original Message -----
From: "Christopher Bartling" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Thursday, December 21, 2000 6:11 PM
Subject: Comunicating between EJBs and Application Client
> 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.
