The current Assumption is that the DeployableContainer is the final target. While that works great for ApplicationServers, there are cases where a Service running on the ApplicationServer is one of the Targets.

e.g. a BPM Engine that runs on WLS/WAS/JBossAS etc but has it's own deployment mechanism for deploying the Process definitions.

Currently we would have to create a DeployableContainer impl for each BPM+ContainerX combination to support Managed mode of the Host Container.

In this case the BPM Container should be able to inherit configuration and depend upon the Host Container. e.g. Host runs on IP-X, BPM Container shouldn't need to be reconfigured with the Host IP by the user. When the Host is stopped, the BPM Container should be stopped first.

The interesting usecase is where you have a BPM process that rely on Resources/Services in the Host Contianer. By having them linked you could deploy e.g. WebServices to the Host and Processes to the BPM that interact with the WebServices.