Won't he also need the ejb-ref entries for ejb to ejb lookups?
ejb-jar.xml-
<ejb-ref>
<ejb-ref-name>ejb/OfficeEJB</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<home>com.tallan.odtos.ejb.office.OfficeEJBHome</home>
<remote>com.tallan.odtos.ejb.office.OfficeEJB</remote>
</ejb-ref>
jboss.xml-
<ejb-ref>
<ejb-ref-name>ejb/OfficeEJB</ejb-ref-name>
<jndi-name>ejb/OfficeEJB</jndi-name>
</ejb-ref>
> -----Original Message-----
> From: Schouten, Andreas [mailto:[EMAIL PROTECTED]]
> Sent: Monday, April 30, 2001 10:51 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-user] Home and remote classes for EJB to EJB call
>
>
> Wy do You deploy the 10 beans in 10 jars? If You deploy them
> all into one
> jar You can call all interfaces.
>
> If You need them in different jars, check out the
> <resource-ref> tag for
> ejb-jar and register the nessasary references to the container..
>
>
> > -----Original Message-----
> > From: Guy Rouillier [SMTP:[EMAIL PROTECTED]]
> > Sent: 30 April 2001 21:07
> > To: JBoss User
> > Subject: [JBoss-user] Home and remote classes for EJB to EJB call
> >
> > Following the discussion on this mail list, I tried my hand
> at getting one
> > EJB to call another. When the client invoked the first EJB, I got a
> > remote
> > exception because the first one could not locate the home and remote
> > interface for the second. So I modified the jar for the
> first EJB to
> > include the home and remote interface classes for the 2nd, and then
> > everything worked fine.
> >
> > Is there any way to get JBoss (or generic app server) to
> use the home and
> > remote classes that are included in the jar for the first
> EJB? This can
> > get
> > out of hand quickly if I have to include the home and
> remote interfaces
> > classes in every jar that invokes a particular EJB; if I
> have 10 EJBs
> > calling another EJB, I would need to have the home and
> remote interfaces
> > for
> > that last EJB in all 10 jars. And the code is already
> running in the same
> > instance of JBoss, although I realize to generalize this
> assumption cannot
> > be made. If not, can I leave the home and remote interface
> classes ** out
> > of ** the jar for the first EJB and put it into a JAR in the lib/ext
> > directory, so I only need to have one copy of the home and remote
> > interfaces
> > classes on a single instance of JBoss? Or must the home and remote
> > interfaces be in the jar for the corresponding EJB?
> >
> >
> > _______________________________________________
> > JBoss-user mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/jboss-user
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
