> > this happening now in 3.2 or 3.0, is it being done in 4.0? > I don't think so. I don't understand what you mean here. If I have an > [expanded] .ear with > > entities.jar > sessions.jar > webstuff.war > > I think I should be able to redeploy: > > webstuff.war > > or > > webstuff.war and sessions.jar > > or all three. In all cases, I don't see why the .ear should be > "redeployed" (maybe there's something else in it that all of these depend on). > The ear DeploymentInfo has references to the subdeployment DeploymentInfo objects. How are these being updated when a subdeployment is redeployed? That is what I'm referring to.
> Also, I don't see what will happen in your scheme if > > ejbsA.jar and ejbsB.jar both reference lib.jar in their manifest > classpaths. > > Am I missing the point? I really don't see how to make this work without > disabling the manifest classpath stuff, which as you point out, can't > simply be ignored. There will be a UCL_ejbsA.jar, UCL_ejbsB.jar and a UCL_shared(lib.jar) that is the parent class loader for both UCL_ejbsA.jar and UCL_ejbsB.jar. Since the parent delegation model takes precedence over the manifests this resolves the type problem as UCL_shared(lib.jar) contains all referenced jars. By virtue of there only being one class loader package protected access problems disappear. ------------------------------------------------------- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
