On 19 May 00, at 15:30, Oleg Nitz wrote:
Hi Oleg,
> No, still no. Let's put to the vote ;-)
>
Let's not do this quite yet. It is important that we be 100%
compliant if possible, and this cannot be achieved by democracy,
but only by engineers.
So, is it legal to deploy a jar with no "ejb-link" in a referenced
bean? You and I think yes. As it turns out, Rickard thinks yes too
(I misunderstood him on this point yesterday):
>> It's nice, jboss conform to the specification here, but don't say
that
>> during deployment EJB reference must contain ejb-link.
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.
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).
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.
-Dan
P.S. Not a vote, just an argument. :-)
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
