[
https://jira.jboss.org/jira/browse/JBAS-7047?page=com.atlassian.jira.plug...
]
Pete Muir commented on JBAS-7047:
---------------------------------
I'm still not seeing any change of behavior in the latest 5.2 snapshot downloaded from
hudson. The exception received client side is an IncompleteDeploymentException which
contains a the contextsInError. The context in error that relates to WebBeansBootstrapBean
contains the root cause of the exception.
See
http://anonsvn.jboss.org/repos/webbeans/ri/trunk/jboss-tck-runner/src/tes...
for the way I extract the exception. Is this correct?
Deployers hide exception cause stack
------------------------------------
Key: JBAS-7047
URL:
https://jira.jboss.org/jira/browse/JBAS-7047
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Reporter: Pete Muir
Assignee: Ales Justin
Priority: Critical
Fix For: JBossAS-5.2.0.Beta1
Currently the deployers unwrap all deployment exceptions to the root cause, and store in
incompleteDeployments. This means we can't check for exception wrapping
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira