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

Input request XML is not correctly generated by PRPC 7.1.7



User is on PRPC 717. The input request XML created by PRPC 717 is not correctly generated due to which the SOAP Service call is failing. They have found that same SOAP service call works correctly in PRPC 6.1 SP2 environment and also when using SOAP-UI.

Error Messages

org.xml.sax.SAXException: WSWS3279E: Error: Unable to create JavaBean of type Missing default constructor? Error was: java.lang.InstantiationException: Message being parsed:

Steps to Reproduce

  1. Consume the WSDL file provided for the SOAP service.
  2. Generate the Connector rules using the SOAP Integration wizard.
  3. Create an activity and set appropriate properties in the activity required for calling the SOAP service.
  4. Call the Connect-SOAP rules through the activity.
  5. The SOAP service call fails with the reported error message.

Root Cause

The root cause of the issue is identified as a misconfiguration/defect in the the custom application code or rules used by user. The values of the properties set in the activity were configured incorrectly. Also, a wrong property was mapped under the node in XML Stream rule.


The following steps helped to resolve the issue:
  1. Set the properties appropriately with their correct values as expected by the SOAP service.
  2. Go to Pages and Classes tab and set the correct class type for the step page used in the activity for setting the properties.
  3. Go to the XML Stream rule and map the correct property under the node as expected by Service. Any incorrect mapping of properties in the XML Stream rule will generate a wrong SOAP request envelope.
Suggest Edit

Published February 9, 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