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

Connection SOAP Wizard Stuck on Class Conflicts Page



Developers are unable to move past the SOAP connector interface wizard screen for class conflicts. The screen highlights several classes that have long names, and apparently requires name changes.

Error Messages


Steps to Reproduce

Run the SOAP connector interface wizard to import a WSDL.

Root Cause

The root cause of this problem is due to the fact class names are restricted to 64 characters in length in PRPC. The SOAP connector interface wizard generated names based on information in the supplied WSDL; however, the names based on the WSDL content exceeded the 64 character restriction. 


The explanation for this behavior is as follows: Class names were shorted to less than 64 characters in the class conflicts screen and this solved the problem. 
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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