Re: how does a deserializer problem come from?

[Brian Ewins]

It may well mean the soap response is not okay. A fairly common cause of such problems is seeing html error pages (with a 200 Ok response code) instead of being sent soap, due to bad service design[1].

Try contacting the soap service via a tunnel (eg the one supplied with Axis, or Nettool from CapeClear[2]) and look at whats coming over the wire.

If you want a specific exception explained, you'd be better just sending in the stack trace.

Hope this helps
Baz

[1]http://nagoya.apache.org/eyebrowse/ReadMsg?[EMAIL PROTECTED]&msgId=643366
[2]http://www.capescience.com/articles/using_nettool/

Jue (Jacky) Shu wrote:

hi all,
if we get deserializer problem, does that mean soap response is okay, but the client don't know how to recognize the return?
thx.
jacky