If you're using document style, then you can validate the message against the schema. If you're using RPC style, it's less convenient to validate, because you must validate each individual parameter type, and you need to check by eye whether the parameters are in order.
You can also use a diagnostic tool like Mindreef SOAPScope. Anne On 7/16/07, Tracey Annison <[EMAIL PROTECTED]> wrote:
We have Java webservices implemented with Spring and Axis, and we are recieving SOAP messages from an external party. When they get the format of these messages wrong, they don't know how to fix them unless we tell them what they got wrong... joy... So we have to check the XML of the message against the service and its WSDL, and pick out what they did wrong - there's a bad type, or a misnamed parameter, or whatever. This is not a trivial task to do by eye, especially as the parameters may not be in the correct order! I'm sure there must be some utility somewhere that can check this for us, and pick out where the mismatches are, but I can't seem to find such a thing. Has anyone ever heard of one? Cheers Tracey Annison ---------------------------------------------------------------------- The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution, or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. TriSystems Ltd. cannot accept liability for statements made which are clearly the sender's own.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
