[arquillian-issues] [JBoss JIRA] (ARQ-742) Print the name of the container in the "Could not deploy to container" exception.

Ondrej Zizka (JIRA) jira-events at lists.jboss.org
Fri Feb 10 23:07:48 EST 2012


     [ https://issues.jboss.org/browse/ARQ-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ondrej Zizka reassigned ARQ-742:
--------------------------------

    Assignee: Aslak Knutsen

    
> Print the name of the container in the "Could not deploy to container" exception.
> ---------------------------------------------------------------------------------
>
>                 Key: ARQ-742
>                 URL: https://issues.jboss.org/browse/ARQ-742
>             Project: Arquillian
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Base Implementation
>            Reporter: Ondrej Zizka
>            Assignee: Aslak Knutsen
>
> In multi-container tests, this exception lacks information about what server it failed to deploy to:
> {code}
> 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)
> ...
> {code}
> 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:
> {code:java}
> throw new DeploymentException("Depoying of <deployment-name> to <container-name> failed: \n       " + e.getMessage(), e);
> {code}

--
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

        


More information about the arquillian-issues mailing list