the SOAP standard specifies that (when used over HTTP) faults should be
returned using response code 500. ATM a generic exception is thrown by
activeSOAP in this case which makes it impossible to diagnose faults (as
opposed to other protocol errors) and unmarshall their content.

one approach would be to create a specific exception associated with the
http transport that allows programmatic access to information that's
required to diagnose and unmarshall SOAP faults.

if this would fit into the activeSOAP design, i'm willing to contribute
a patch.

- robert