Let's start with the requirements considering what the j2ee specs allow and how we want to improve on any deficiencies. Most importantly we need to get to a point where we ourselves understand how to achieve any level of class loader hierarchy, from flat to compound given a canonical deployment package.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "lsanders" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, April 19, 2002 9:30 AM Subject: Re: [JBoss-dev] [ jboss-Bugs-544848 ] EAR Deployments don't work > > I agree. I think each deployment type should be able to dictate what url's > to expose to the UnifiedClassLoader, and which to keep privately within > child URLClassLoaders. A simple hacked solution would be to remove the > createClassLoaders from DepoymentInfo, and place that responsibility in the > init methods of SubDeployer (with SubDeployerSupport providing the default > implementation). I have been looking into a Deployer refactoring anyway... > I'll put some time into it this weekend, and present a list of requirements > / proposed design for discussion. > > -Larry > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
