Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

SOAP service deployment issue after PRPC 5.4 to Pega 7.1 upgrade

SA-8880

Summary



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
<complexType name="pagedata">

Value in Pega 7.1.5
<complexType><sequence><element name="RequestValidateAddress" type="ns1:App"/>

Error Messages



Not Applicable

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.


Root Cause



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.


Resolution



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.

Published June 12, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us