On 18 May 00, at 9:49, marc fleury wrote:
> >
> > If, on the other hand, the optional ejb-link field is not provided, the
> > deployer must manually bind the name of the ejb-ref to a global-
> > namespace name that has an appropriate associated bean.
>
> Again with Dan on this... no-nonsense defaults is our Rule #1.
>
> The link is optional because in the case there is one datasource
> (95%cases) your stuff is overkill, even BEA WL does it like that AFAIK
> (but you are the WL power user of the year Rickard;-). Implicit is
> possible and good because simple. Simple is good. Again check
> ContainerMetaData for code, trivial adaptation with your MLET thingy and
> the tag of the type.
>
Hi Marc,
Three minutes in the e-mail penalty box for you for not reading
closely enough! :-) Now we're talking about EJB references, not
data source references (on which we are all in complete agreement
so no more need be said). The issue is a little technical point on
mapping EJB references into the global namespace.
(But thank you for agreeing with me anyway. I can't get enough of
that.)
-Dan
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
