Fault Handling
Sometimes things don't go OK. If so, there's never a response and a fault; you can't have it both ways. The fault looks just like a body except it says it's a fault. When the fault is a server fault and the server is a Java implementation, most of the time the fault includes an exception stack trace inside. However how well the errors are represented and handled is very implementation specific.
  • An error condition is a fault
  • The fault is the only thing in the response body
  • Type of faults:
    • VersionMismatch
    • MustUnderstand
    • Client
    • Server
Slide 18 of 58 Contents
  1 |   2 |   3 |   4 |   5 |   6 |   7 |   8 |   9 | 10
11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20
21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30
31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40
41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50
51 | 52 | 53 | 54 | 55 | 56 | 57 | 58
www.arachna.com > Educational Resources > Tutorials > O'Reilly Open Source Conference (2002) > Exchanging Objects and Messages With SOAP

spidaman
© 2002-2009 Ian Kallen | Copyright Notice