Handling SOAP faults with Form Builder forms?

Hi. I've successfully consumed a webservice using the approach described by http://wiki.orbeon.com/forms/doc/user-guide/form-builder-user-guide/http-services

Now I need to implement error handling. Does anyone know how I can handle SOAP fault scenarios when consuming SOAP services using Form Builder?

Any pointers would be very much appreciated. Thanks.

-Stian

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

I don't yet use orbeon PE with its built in services GUI for defining web services requests.  
So I've been reading up on how to debug hand coded  SOAP submissions and exceptions in orbeon CE.

I'm not sure yet how to write the orbeon code to catch SOAP returned fault messages.  
I guess this is what you're asking.   I'll be interested to learn more.

Here are further notes which might help testing during compile time.

.......

SoapUI is a very useful tool for testing a web service at compile time.

http://www.soapui.org   (free edition)

You can create a project profile .. new soapUI project

then paste the orbeon
<soapenv:Envelope> .. </soapenv:Envelope> from your xform
into one of the exposed service operations requests.

Submit the soap envelope to the exposed service and monitor the request (including any errors)

Here is an example web service I'm testing ..

http://graphical.weather.gov/xml/SOAP_server/ndfdXMLserver.php

I saw this error message in orbeon call stack which did not offer any clues

"Program degrib returned no data"

A google search soon unearthed the cause ..

http://tech.groups.yahoo.com/group/NDFD_SOAP_Service/message/1182

The error I had made was to insert a historical date into startDate field .. which returns an error since this is a weather forecasting service (requiring dates in the future not historical).

If you try that you will see the fault response.   But the error was not clear from the orbeon call stack.

.......

Another tool I've found is burbsuite as proxy server when the orbeon server is being tested.  
I've used Fiddler2 on Windows but it is not available on ubuntu which I'm using for development.

http://portswigger.net/burp/

The default port in burpsuite is 8080 so you will need to change this to 8888 or other port to avoid clashing with orbeon.

I haven't yet mastered burpsuite so I'm keeping it in reserve to try out later as a proxy server.

Here is a burp reference ..

http://resources.infosecinstitute.com/burp-suite-walkthrough/

and SOAP fault example ..

http://www.tutorialspoint.com/soap/soap_fault.htm