[
https://issues.jboss.org/browse/ARQ-1010?page=com.atlassian.jira.plugin.s...
]
Aslak Knutsen updated ARQ-1010:
-------------------------------
Description:
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.
was:
The current Assumption is that the DeployalbeContainer 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.
Support for 'Guest/Nested' Containers
-------------------------------------
Key: ARQ-1010
URL:
https://issues.jboss.org/browse/ARQ-1010
Project: Arquillian
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Base Implementation, Deployable Containers SPI
Affects Versions: 1.0.1.Final
Reporter: Aslak Knutsen
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira