complex deployment

[Kirk Pepperdine]

I'm trying to devise a way to support the deployment of an application that has been written by several teams. Each of the teams has developed a portion of the appliction that will contain web and ejb components. One team has provided some technical services that are being used by the others. What I'm trying to do is pre-deploy the technical services so that the other teams don't have to. What I'm finding is that the other teams are not able to deploy into this environment because... the units of deployment (war or jar) get loaded into totally seperate class loaders. So, I've been looking to see if I can specify that the technical services be in a parent classloader (not the system classloader).

If anyone has any advice on how to support a complex development environment, I'd be sure happy to listen to it.

TIA,
Kirk

[Rovas Kram]

Should work if your technical services are either ejbs or classes within the ejb jars and these ejb jars are deployed to the same application as the web apps. In other words, all WebComponents should have access to all EJBComponents within the same Application.

[Sachin Dangi]

You can create custom class loader hierarchies in wls8.1

However while deciding any approach please keep in mind that if the same class is loaded by 2 class loaders then you may get class cast exception when object created by one class loader is assigned to reference of the same class loaded by another class loader.
[ September 02, 2004: Message edited by: sachin ]