As I understand it, that's exactly what's happening, but if I want to pass a "Customer" object to the service, I'll have to serialize it to an org.w3c.dom.Element before passing it through the WS Client proxy, no? In case I'm totally missing the boat, here is some WSDL:
As you can see, it doesn't tell me much about the structure of the XML Document I'm supposed to give as a parameter to, say, the SetUser service. It just says "any". But I'm told it expects an XML document, formatted according to this schema:
To be honest, the only part I've tried so far is to convert a returned XML Document (from the GetUserHeirarchy service) into a local object via JAXB. As far as I can tell, this is not automatic (or else I'm doing it wrong. Example:
Anyway, I can't even
test that code now, because of
this other problem I'm having right now.
BUT: If you can suggest a way for me to "fix" the WSDL so that JAX-ws detectes that the service expects an XML document in that parameter, or, better yet, supply the schema for that XML document
directly in the WSDL, you will have made me a very happy man. I don't control these WSDLs or Schemas myself (as I hope you can tell from all the proprietary microsoft crap inside them), but I'd love to be able to supply some suggestions to our M$ consultant on how to improve our interoperability...
Thanks for you genius, as always, Peer!
[PR: added line breaks to schema to minimize page width]