[
https://issues.jboss.org/browse/AS7-1198?page=com.atlassian.jira.plugin.s...
]
Jason Porter commented on AS7-1198:
-----------------------------------
I looked into this a little bit Jason a few months back. You'd have to parse the
message and try to recreate the exception because the exception that ARQ gets is a new
exception and doesn't wrap the actual exception. It would be much easier if the
reported exception was part of a chain instead of new exception simply containing text
about the causes.
Add a Deployment Exception Transformer for the Arquillian container
-------------------------------------------------------------------
Key: AS7-1198
URL:
https://issues.jboss.org/browse/AS7-1198
Project: Application Server 7
Issue Type: Feature Request
Reporter: Jason Porter
Fix For: Open To Community
A discussion on IRC:
http://echelog.matzon.dk/logs/browse/jbosstesting/1309903200
We're not reporting back to ARQ users the actual error during deployment, just
whatever the app server gives us.
--
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