It says must right at the start of 1.4.3.1.1 when describing the bean provider's
responibilities:
"The Bean Provider must use EJB references to locate the home interfaces of other
enterprise beans as
follows.
. Assign an entry in the enterprise bean's environment to the reference. (See
subsection 14.3.1.2
for information on how EJB references are declared in the deployment descriptor.)
. The EJB specification recommends, but does not require, that all references to other
enterprise
beans be organized in the ejb subcontext of the bean's environment (i.e. in the
java:comp/env/ejb JNDI context).
. Look up the home interface of the referenced enterprise bean in the enterprise
bean's environ-ment
using JNDI."
It also says the environment must be specified using the ejb-ref tag at the start of
1.4.3.1.2
"Although the EJB reference is an entry in the enterprise bean's environment, the Bean
Provider must not
use a env-entry element to declare it. Instead, the Bean Provider must declare all the
EJB references
using the ejb-ref elements of the deployment descriptor."
----- Original Message -----
From: "Taylor, Jeremy" <[EMAIL PROTECTED]>
To: "'jBoss'" <[EMAIL PROTECTED]>
Sent: Tuesday, January 16, 2001 1:53 AM
Subject: RE: [jBoss-User] ejb-ref in deployment descriptor
> The 1.1. spec. section 14.3 says that EJB references "allow" the Bean
> Provider to refer to the homes of other enterprise beans. I have not yet
> found anywhere that says that Bean Providers must only use EJB references -
> perhaps someone could enlighten me.
>
> I think that using EJB references is good practice and would not mind if
> they were made mandatory for all references but it is hard to see how this
> could be achieved.
>
> -----Original Message-----
> From: Scott M Stark [SMTP:[EMAIL PROTECTED]]
> Sent: 16 January 2001 03:19
> To: jBoss
> Subject: Re: [jBoss-User] ejb-ref in deployment descriptor
>
>
> Hi Dan,
>
> On re-reading the 1.1 spec I have to say your definitely correct and
> it makes sense.
> Without this the jndi names are a big dependency/management problem.
>
> Thanks.
>
> > Hi Scott,
> >
> > My understanding is that ejb-refs are required for all bean
> > references. These references are then bound to actual ejb
> > components (inside or outside the application) at deployment time.
>
> > The optional ejb-link element can be used to "pre-bind" a
> reference
> > to a particular ejb within an application.
> >
> > The disadvantage of treating an EJB component as "just another
> > client" that can use the JNDI namespace to look up an arbitrary
> > bean is that this hurts the EJB component's portability. In other
> > words, the lookup would be dependent on a particular deployment
> > environment (i.e. the bean it needs is available under name x),
> > rather than being dependent only on the availability of a
> particular
> > service (i.e. a home and remote interface) available under any
> > arbitrary name.
> >
> > The EJB 2.0 spec goes so far as to describe how home interface
> > references in the deployment descriptor should be bound to a
> > CosNaming service, for interoperability between application
> servers.
> >
> > -Dan
>
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> List Help?: [EMAIL PROTECTED]
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> List Help?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
