The ejb-ref allows the bean provider to code to use a local name which is
resolved to an actual name at deployment time.
You don't have to use them.
-----Original Message-----
From: Mattias V. Bertelsen [SMTP:[EMAIL PROTECTED]]
Sent: 15 January 2001 06:29
To: [EMAIL PROTECTED]
Subject: [jBoss-User] ejb-ref in deployment descriptor
Are <ejb-ref> entries in the deployment descriptor *required* for an
EJB
to be able to look up another EJB using JNDI? I want to write a
session
bean that looks up other session and entity beans, without knowing
ahead
of time which particular ones it will be using. All of the required
interface classes will be available to the classloader, but I won't
know
which particular ones that this bean would access (I want ALL of
them to
be available). However, I have a suspicion that those <ejb-ref>
entries are important in setting up the JNDI context for the bean.
Is
this true? Do I really have to put an <ejb-ref> entry for every
bean
that it could possibly contact?
Thanks,
Mattias V. Bertelsen
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
