Bug 779825 (SOA-2186)

Summary:	Wise SOAPClient fault behaviour is undocumented
Product:	[JBoss] JBoss Enterprise SOA Platform 5	Reporter:	Jan Ypma <jypma>
Component:	Documentation, JBossESB	Assignee:	David Le Sage <dlesage>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	5.0.2
Target Milestone:	---
Target Release:	5.1.0 GA
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-2186
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	n/a (documentation issue)
Last Closed:	2011-02-01 04:42:48 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jan Ypma 2010-07-28 08:35:05 UTC

Affects: Documentation (Ref Guide, User Guide, etc.)
Complexity: High
Help Desk Ticket Reference: https://access.redhat.com/jbossnetwork/restricted/caseDetail.html?caseId=1178003
project_key: SOA

The documentation of the wise SOAPClient does not specify it's behaviour when the web service being called generates a SOAP fault. In actuality, the SOAPClient throws an ActionProcessingException with the SOAP fault as actual fault. This should at least be documented in the SOA-P programmers guide. It should also be mentioned that by default this error will not be returned when being called via SOAP ourselves (see below), and that there will be no redelivery when being called via JMS (since it's not a RuntimeException).

This default behaviour does cause problems when using the SOAPClient within an ESB-published web service endpoint itself. Apparently the "faultTo" EPR doesn't get set for exposed web service end points (which might be intended, or a different defect).

See https://access.redhat.com/jbossnetwork/restricted/caseDetail.html?caseId=1178003 for discussion.

Comment 1 Anne-Louise Tangring 2010-09-21 17:52:26 UTC

This is a candidate for SOA 5.1.0. not committed. Investigate if we need to provide better documentation on how fault handling works.

Comment 2 Jan Ypma 2010-09-22 12:13:29 UTC

I originally raised this issue, together with SOA-2188. Do let me know if/how I can help out with writing a bit of docs on the subject.

Comment 3 Kevin Conner 2010-09-22 12:25:06 UTC

The behaviour of exception processing should already be documented in the programmers' guide, this task would just defer to that part.

Comment 4 Anne-Louise Tangring 2010-12-06 16:26:19 UTC

Usability and customer sat is important, thus this is made a blocker for SOA 5.1.

Comment 5 Dana Mison 2010-12-17 01:52:08 UTC

Labels: Added: ESB_Programmers_Guide
Complexity: Added: High

Comment 7 Dana Mison 2011-01-05 00:12:16 UTC

Writer: Added: Darrin

Comment 8 Dana Mison 2011-01-27 10:00:53 UTC

this might have already been done upstream - please check

Comment 10 Dana Mison 2011-02-17 11:54:21 UTC

Writer: Removed: Darrin Added: dlesage

Comment 11 David Le Sage 2011-02-18 01:45:21 UTC

Release Notes Docs Status: Added: Documented as Resolved Issue
Release Notes Text: Added: https://issues.jboss.org/browse/SOA-2186

The ESB Programmers' Guide documentation on exception processing behaviour has been updated to reflect that the SOAPClient throws an ActionProcessingException when a web service that is being called generates a SOAP fault. Note that redelivery doe not occurs when the web service is called through the JMS. This is because it is not a RuntimeException.

Comment 12 David Le Sage 2011-02-18 01:55:00 UTC

Release Notes Text: Removed: https://issues.jboss.org/browse/SOA-2186

The ESB Programmers' Guide documentation on exception processing behaviour has been updated to reflect that the SOAPClient throws an ActionProcessingException when a web service that is being called generates a SOAP fault. Note that redelivery doe not occurs when the web service is called through the JMS. This is because it is not a RuntimeException. Added: https://issues.jboss.org/browse/SOA-2186

The ESB Programmers' Guide documentation on exception processing behaviour has been updated to reflect that the SOAPClient throws an ActionProcessingException when a web service that is being called generates a SOAP fault. Note that redelivery does not occurs when the web service is called through the JMS. This is because it is not a RuntimeException.

Comment 13 David Le Sage 2011-02-18 01:55:15 UTC

Release Notes Text: Removed: https://issues.jboss.org/browse/SOA-2186

The ESB Programmers' Guide documentation on exception processing behaviour has been updated to reflect that the SOAPClient throws an ActionProcessingException when a web service that is being called generates a SOAP fault. Note that redelivery does not occurs when the web service is called through the JMS. This is because it is not a RuntimeException. Added: https://issues.jboss.org/browse/SOA-2186

The ESB Programmers' Guide documentation on exception processing behaviour has been updated to reflect that the SOAPClient throws an ActionProcessingException when a web service that is being called generates a SOAP fault. Note that redelivery does not occur when the web service is called through the JMS. This is because it is not a RuntimeException.

Comment 14 David Le Sage 2011-02-18 01:56:25 UTC

Release Notes Text: Removed: https://issues.jboss.org/browse/SOA-2186

The ESB Programmers' Guide documentation on exception processing behaviour has been updated to reflect that the SOAPClient throws an ActionProcessingException when a web service that is being called generates a SOAP fault. Note that redelivery does not occur when the web service is called through the JMS. This is because it is not a RuntimeException. Added: https://issues.jboss.org/browse/SOA-2186

The ESB Programmers' Guide documentation on exception processing behaviour has been updated to reflect that the SOAPClient throws an ActionProcessingException when a web service that is being called generates a SOAP fault.