Hi!
Toby Allsopp wrote:
> > marc fleury wrote:
> >>
> >> what above "reasoning"... the fact that I don't put in XML the
> >> dependencies?...
> >
> > Yes. The classloader tree needs to be explicit as it cannot be inferred
> > from any other info in the applications.
>
> Is this really true? Would it not be possible to figure out what classes
> need to be shared from ejb-refs and then pull all of those out of the
> individual EARs (so that they're not picked up by the leaf classloaders)
> and put them in the logical application's parent classloader?
No, because it might also be the case that you *want* class duplication
in parallel subtrees (for versioning). I.e. two EAR's can communicate
through a parent EAR's classloader but they both have their own versions
of a class that the parent EAR does not have.
Also, there's still the fact that you cannot dereference ejb-links
without knowing in which EAR's to look. If you say "look in all deployed
EAR's" then that means that you can only have one application deployed
at any one time, since two applications may have beans with the same
EJB-name.
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
