Kbase P115624: An OpenEdge 10.1x client produces error 11773 when accessing an OpenEdge 10.0B Document/Literal Web
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/31/2009 |
|
Status: Unverified
SYMPTOM(s):
An OpenEdge 10.1x client produces error 11773 when accessing an OpenEdge 10.0B Document/Literal Web Service
Error receiving Web Service Response: Wrong member during the '[null]{urn:OpenEdgeServices:NewCoService-WrappedDocLiteral:NewCoService-WrappedDocLiteral}' unwrapped sequence deserialization. (11773)
There is an extra "result" element in the SOAP Response
The "result" element is not described in the WSDL document
The Web Service call works fine when using the OpenEdge 10.0x style
FACT(s) (Environment):
OpenEdge 10.0B
OpenEdge 10.1x
All Supported Operating Systems
CAUSE:
Bug# OE00107581
CAUSE:
Release Note# 100B-00173
CAUSE:
To create an OpenEdge Web Service, you must first generate a Web Service definition using ProxyGen and then deploy that definition (.wsm file) to the WSA. If the same encoding is not used during the generation and deployment of the .wsm file, then an invalid WSDL document may be generated in OpenEdge 10.0B.
This in turn will cause problems when unwrapping the Wrapped Document/Literal message, because based on the WSDL document the "result" element was not expected.
FIX:
If you wish to (re)deploy a Web Service in OpenEdge 10.0B with a different encoding, then you should generate a unique web service definition for each encoding and deploy them using the encoding with which they were generated.
- OR -
Upgrade your Web Service to OpenEdge 10.1A. You will then be able to change the encoding between generation and deployment without producing invalid WSDL documents.
- OR -
As a workaround use the OpenEdge 10.0x style to make Web Service calls from the OpenEdge 10.1A client (bprowsdldoc -show100style).