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]
