Re: [jBoss-Dev] Complex J2EE Deployment was RE: Proposedrefactoring...

[Dan OConnor]

On 19 Dec 00, at 9:15, Rickard �berg wrote:


> If we add the "system" notion, then the EAR metadata would have a parent
> too, so the ejb-ref's that an ejb-link can resolve to is the transitive
> closure of the entire system.

I wanted to make a small suggestion for this new and improved
deployment facility about which we've been talking. I think it would
be great if it supported the new <ejb-link> syntax, which allows
bean references to use a path name within an EAR file prepended
to the bean name and separated by #. (See 9.3.2 of the proposed
final EJB 2.0 draft.)

Also, I wanted to point out that the use of <ejb-link> to refer to an
EJB outside of the current EAR is non-compliant, so applications
that used such a feature wouldn't be portable. IMHO if you want to
link to a bean in a different EAR, jboss should only support this in
our jboss-specific xml file. That way we won't encourage non-
portable deployment descriptors. However, I can see the ease-of-
use argument for the other point of view.

-Dan