Re: [Babeldoc-devel] SOAP: missing Exceptions

[Hans B. <ben...@ch...>]

On Mon, 7 Apr 2003, Bruce McDonald wrote:

> Unfortunately this pipelinestage has not recieved all the attention that
> other stages have.  I would welcome suggestions as to how to address
> these kinds of issues.

Bruce,

I took some time reading the sources of Apache SOAP. The http status is
read somewhere down in org.apache.soap.util.net.HTTPUtils and then
ignored. So it is not accessible from the point where you call
the send method of org.apache.soap.messaging.Message. And even the parsing
of the (html) error message of the server does not lead to an
SOAPException.

The only way I see to fix this, is to use another SOAP API. My suggestion
is to switch to Sun's JAXM/SAAJ API, which throws a SOAPException when
encountering an 404 error. The rewrite of the SOAPWriterPipelineStage
should not be to difficult, but I have not yet looked at the two other
classes. Is any of the other modules using the SOAP API?

Concerning real SOAP faults, it seems that the client, i.e. the
pipelinestage, has to check the SOAP response for them, and then throw an
Exception by itself.

If you agree, I could do the rewrite as well as the additional fault
handling. But probably you don't want to have too many changes before the
1.0 release... Maybe, we should only add the fault handling and keep the
rewrite for later?

Regards,
Hans