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

[Rickard �berg]

Hi!

"Jung , Dr. Christoph" wrote:
> So the first thing that is fairly easy to do, is to have that general
> DeployerMBean interface and a general DeploymentException (first proposal
> attached: main extension is that the deployers now also expose an
> un/is/deploy(URL) method, a deploy(URL,ClassLoader) method that explicitely
> takes the parent ClassLoader as an argument, and a whereDeployed(URL) method
> that returns the actual ClassLoader into which this part of the application
> has been put.)

You're pretty much on target, except the second parameter should be the
EAR metadata and not a classloader. Then, the classloader is one aspect
of that metadata. This will allow the ContainerFactory to resolve
ejb-link's easily: check in "self" and all EJB JAR's that can be reached
by going to the EAR metadata.

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.

/Rickard

-- 
Rickard �berg

Email: [EMAIL PROTECTED]