|
We've been seeing some problems with SOAP clients
that use WSDL to access web services. It seems that if we change the order of
some of the WSDL elements that things start to work.
What we're wondering is if this is a legitimate
problem, or is it just a problem with SOAP clients that have implemented the
WSDL parser too rigidly. It looks when the output is defined before the
input and not paired with each other that we see the most problems.
The question is: "Is there an implied order and/or
pairing to the <message> elements that define the input and output
for a method?"
Thanks,
Grant
|
