Details
-
Enhancement
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
Description
In multi-container tests, this exception lacks information about what server it failed to deploy to:
org.jboss.arquillian.container.spi.client.container.DeploymentException: Could not deploy to container: {"JBAS014671: Failed services" => {"jboss.ejb3.dd-based-ejb-client-context.\"client.jar\"" => "org.jboss.msc.service.StartException in service jboss.ejb3.dd-based-ejb-client-context.\"client.jar\": Failed to start service"}}
at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:74)
at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:142)
at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:156)
at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:123)
at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:266)
at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:122)
...
The exception is thrown in the ArchiveDeployer, but the implementation of DeployableContainer doesn't get this information so Arq must be changed itself.
I suggest to throw an exception somewhere in ContainerDeployController with a message of this form:
throw new DeploymentException("Depoying of <deployment-name> to <container-name> failed: \n " + e.getMessage(), e);
Attachments
Issue Links
- blocks
-
WFLY-576 Testsuite tasks (tracking)
-
- Closed
-
