WSDL exception ‘Invalid clipboard stream’ for complex data types
Your generated WSDL from a Pega 7.1.7 SOAP Service throws an exception mapping inbound data
(invalid clipboard stream detected).
com.pega.pegarules.pub.services.InboundMappingException: Caught unexpected exception mapping inbound data: Invalid clipboard stream detected in module
Steps to Reproduce
- Create a SOAP service in Pega 7.1.7 using a response parameter of pageList for complex type.
- Note the naming convention in the generated WSDL.
The root cause of this problem is a backward-compatibility defect in Pegasystems’ code/rules.
In the Pega 7.1.5 SOAP Service, the Pega-generated WSDL for complex types uses uppercase "T" in Type.
However, Pega 7.1.7 uses a lowercase "t".
The Pega 7.1.5 naming convention changed in Pega 7.1.7
Perform this local change:
Manually rename the complex type.
Until the defect is corrected in a future release, modifying generated WSDL from Pega 7.1.7, will keep your inbound data mapping error-free and synchronized with your earlier implementations.
The defect correction will revert to the previous naming convention (uppercase "T" in Type).
Published July 9, 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.