That should not be happening for wars. The AbstractWebContainer.init(DeploymentInfo) should not be calling its super's init method as this is what triggers that behavior. Neither the 3.2 or 3.0 versions do this.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Jeremy Boynes" <[EMAIL PROTECTED]> To: "Jboss-Development" <[EMAIL PROTECTED]> Sent: Saturday, December 14, 2002 5:36 PM Subject: [JBoss-dev] Nested deployments in WAR > I have a war file which contains other deployable units as resources > intended to be served to clients. For example, the war contains > /files/server/default/deploy/petstore.ear > /files/server/default/conf/jboss-service.xml > > When I deploy this war on JBoss, nested deployment tries to start all these > units. This goes to pieces very quickly as the war contains an actual > configuration (it's intended to be a netboot host). > > Is this the intended behaviour or is nested deployment being too aggressive? > > This is a simple war file, not an ear. > > Thanks > Jeremy ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
