We do something similar to you, in some cases. Since we're not using
WSDL-generated calls, but programmatically configured SOAP calls, in
some cases, we bypass most of the AXIS magic stuff, and end up using
it for little more than transport.
On 25 Jan 2006, at 22:10, Stuart, Jay Cameron wrote:
I did what you suggested using the location attribute and it
worked like a charm. Thank you very much. But now I have another
issue.... The response coming back from the server can be like the
one I previously sketched out, or it could be a fault, like the one
sketched below:
Problem is, then you're running two parses. What you *really* want
to do is to grab the envelope (or body) object as the top element,
and then marshall the fault and/or the other expected objects into
it. That gets around the problem of having two maps for the top
level, returns you to a single SAX operation, and will marshal any of
what's present. In addition, should you choose to, you can throw the
error inside the parse operation during unmarhshalling when the
setter is called on your body payload to set the fault code, with the
body generating an exception containing the fault data, instead of
dealing with actually having to know how the error handling works.
It also means that you can deal with SOAP faults in different ways -
throwing IOExceptions when the faults are IO related, for example.
-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
