+ both war deployer and ejb deployer to examine "ejb-link" first for both "ejb-ref" and "ejb-local-ref".
+ war deployer to have a switch "LenientEjbLink" allowing misconfigured ejb-links to be ignored for backward compatibility. This is set to "false" by default, meaning misconfigured ejb-links will cause a deployment error.
+ war deployer and ejb deployer to support a new element in jboss descriptors called "ejb-local-ref" which contains a "local-jndi-name" element, similar to the "ejb-ref" element. This "ejb-local-ref" in the jboss deployment descriptor is only consulted in the case that the "ejb-local-ref" in the standard descriptor does not contain an "ejb-link" element (or in the case of the war deployer, the "LenientEjbLink" flag has been set and the "ejb-link" contains a name that cannot be resolved).
May I please have my cvs write access back so I can commit?
thanks Jan
Scott M Stark wrote:
Ok, then I agree with adding the ejb-local-ref support.
------------------------------------------------------- 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/bulletproofapps1 _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
