SOAP service deployment issue after PRPC 5.4 to Pega 7.1 upgrade
SOAP service deployment issue occurs after you upgrade from PRPC 5.4 to Pega 7.1.5.
The following value is changed in the WSDL that is generated for the SOAP services. Due to this, Dotnet needs to considerably change the Dot Net class names.
Value in PRPC 5.4
Value in Pega 7.1.5
<complexType><sequence><element name="RequestValidateAddress" type="ns1:App"/>
Steps to Reproduce
1. Create a SOAP service in PRPC 5.4 and upgrade to Pega 7.1.5.
2. Observe that the ComplexType value changes in the WSDL.
The complexType name of “App” that is repeating is an expected behavior.
The complexType definitions are completely different schema definitions and belong to different Class names as specified by the respective targetNamespace attribute.
The .NET client team needs to parse the WSDL to look for the schema elements and their corresponding targetNamespace attribute values (which are unique) rather than the name attribute values defined under the complexType child element.
0% found this useful