Hey
Oleg Nitz wrote:
> Dan OConnor wrote:
> DO> Of course, SOMEHOW that reference must be matched up to an
> DO> actual bean. Agreed? Apart from an ejb-link or a proprietary
> DO> method, what is left? I can see only one other alternative from the
> DO> information in the deployment descriptor reference: the home and
> DO> remote classes. But this is not sufficient, because multiple beans
> DO> with the same home and remote classes may be deployed in the
> DO> same application (with differenent names and perhaps different
> DO> environment entries).
>
> DO> So what is left? My belief is that either the ejb-link mechanism
> DO> must be used, or the reference must be bound to a bean using a
> DO> proprietary method. I don't see any other way.
> What about ejb-ref-name?
> This is the name of the referenced bean that is known to the Bean
> Provider. I think that is most cases the Bean Provider knows the right
> ejb-name of the referenced bean. The ejb-link mechanism should be used
> by Application Assembler only if the ejb-ref-name is wrong
> (e.g., the referenced Bean was renamed, or it was obtained from
> other department).
I just don't see why one would want to introduce such semantics, since
it has no basis in the spec.
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
