[ https://issues.jboss.org/browse/ARQ-697?page=com.atlassian.jira.plugin.sy... ] Geoffrey De Smet updated ARQ-697: --------------------------------- Description: Currently, when something goes wrong in a managed server, such as ARQ-660, you get a meaningless exception "Could not deploy to container". The real exception should be reported, for example "port in use". Furthermore, the message is unclear: how far does this "Could not deploy to container" message stretch? If we have a bug in our CDI configuration (such as an Ambiguous dependency) in our war, will it also be reported with this exception or not? was: Currently, when something goes wrong in a managed server, such as ARQ-660, you get a meaningless exception "Could not deploy to container". The real exception should be reported, for example "port in use". It's furthermore unclear, how far this "Could not deploy to container" stretches: if we have a bug in our CDI configuration (such as an Ambiguous dependency) in our war, will it also be reported as such or not? -- 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

[ https://issues.jboss.org/browse/ARQ-697?page=com.atlassian.jira.plugin.sy... ] Ondrej Zizka reassigned ARQ-697: -------------------------------- Assignee: Ondrej Zizka -- 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