Forum Discussion
pascalSoap
14 years agoOccasional Contributor
Hello,
Thanks for the answer
Don't worry and please don't be bothering :
- No problem for the closing tag, I've learned it for a long time ... and I know XML thanks.
- It seems to me I have guessed the meaning of schema compliance. Just wanted to have confirmation.
- I know for what use is Soap UI, thanks a lot.
Well about the question itself, I have checked with the team I have asked to develop the Web Service : The cause is that they have choosen to send back a Fault Object which contains one more tag than the one specified in the WSDL ; this way it is easier for them to handle the set of error messages server-side. I have checked with the client application developpement team also : There is no impact client-side, the real client application (which is a WebPart component included in a SharePoint site) simply ignores this tag. The Soap UI tool, though, detects there is something unexpected in the response
Salut,
Pascal
PS : je réponds en anglais pour m'entraîner !
Thanks for the answer
Don't worry and please don't be bothering :
- No problem for the closing tag, I've learned it for a long time ... and I know XML thanks.
- It seems to me I have guessed the meaning of schema compliance. Just wanted to have confirmation.
- I know for what use is Soap UI, thanks a lot.
Well about the question itself, I have checked with the team I have asked to develop the Web Service : The cause is that they have choosen to send back a Fault Object which contains one more tag than the one specified in the WSDL ; this way it is easier for them to handle the set of error messages server-side. I have checked with the client application developpement team also : There is no impact client-side, the real client application (which is a WebPart component included in a SharePoint site) simply ignores this tag. The Soap UI tool, though, detects there is something unexpected in the response
Salut,
Pascal
PS : je réponds en anglais pour m'entraîner !