Ok, then I agree with adding the ejb-local-ref support.

--
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx

Jeremy Boynes wrote:
The spec makes the usage optional as well:
"The Application Assembler *can* use the ejb-link element in the deployment
descriptor to link an EJB reference to a target enterprise bean." [EJB2.0 pp
418] Note the use of "can" not "must"

And:
"*If* an EJB reference declaration includes the ejb-link element, the
Deployer *should* bind the enterprise bean reference to the home of the
enterprise bean specified as the link's target." [EJB2.0 pp 420] Again note
"If" and "should"

Finally:
"The Deployer must ensure that all the declared EJB references are bound to
the homes of enterprise beans that exist in the operational environment."
[EJB2.0 pp 420]

So if the target is not there then it is a Deployment error. That seems a
little restrictive if checked at deploy time because of boot order
dependencies and redeployment, but if the target is not present when used
then an error must be raised.

Jeremy

/*************************
 * Jeremy Boynes
 * Partner
 * Core Developers Network
 *************************/



------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to