Hi!
Dan OConnor wrote:
> R�> It doesn't, but any EJB-reference MUST be resolved by
> *either* an
> R�> ejb-link *or* the jBoss mechanism.
>
> Now the second question is, must the EJB reference without an ejb-
> link have a link specified at deployment time by a proprietary
> mechanism? Here you and Rickard disagree, I think.
Correct, because if neither ejb-link or the jBoss-link has been set I
have n idea what to bind it to.. as simple as that..
> Of course, SOMEHOW that reference must be matched up to an
> actual bean. Agreed? Apart from an ejb-link or a proprietary
> method, what is left? I can see only one other alternative from the
> information in the deployment descriptor reference: the home and
> remote classes. But this is not sufficient, because multiple beans
> with the same home and remote classes may be deployed in the
> same application (with differenent names and perhaps different
> environment entries).
The EJX GUI will actually guess which bean the reference should link to,
and will fill in the ejb-link automatically. The same way, if you fill
in ejb-link, EJX will set all the other fields (remote, home, type, and
ref-name).
> So what is left? My belief is that either the ejb-link mechanism
> must be used, or the reference must be bound to a bean using a
> proprietary method. I don't see any other way.
Me neither :-)
/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]
