[
https://issues.jboss.org/browse/JBESB-3643?page=com.atlassian.jira.plugin...
]
Tom Cunningham resolved JBESB-3643.
-----------------------------------
Resolution: Done
tcunning@localhost:product]$ svn commit
Adding
product/services/soap/aop/java/org/jboss/internal/soa/esb/soap/wise/WSMethodInvokeAspect.java
Sending product/services/soap/aop/resources/META-INF/jboss-aop.xml
Sending
product/services/soap/src/main/java/org/jboss/soa/esb/actions/soap/wise/SOAPClient.java
Transmitting file data ...
Committed revision 37426.
WISE SOAPClient exception loss
------------------------------
Key: JBESB-3643
URL:
https://issues.jboss.org/browse/JBESB-3643
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.10
Reporter: Tom Cunningham
Assignee: Tom Cunningham
Fix For: 4.10 CP1
WISE currently captures the exception raised by the WS invocation, and then goes through
a list of exceptions to see if the exception matches those.
What we'd like to do is catch the exception, look inside the
InvocationTargetException, and if it is a javax.xml.ws.soap.SOAPFaultException, wrap it in
the same as other exceptions.
REPRODUCE :
1. Deploy the WAR attached to SOA-3205 file on SOA-P 5.1
2. Unzip the webservice_consumer_wise_smooks.zip into the quickstarts directory
3. ant deploy
4. ant runtest
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira