Property-Set does not encode special characters from connectors
Using the Property-Set method in an activity to map a Connect-JMS response, does not automatically encode special characters (for example, '&' to '&').
Steps to Reproduce
- Run a Connect-JMS rule with special characters in the request.
- Map the response using a Property-Set step in an activity.
Property-Set maps properties directly and hence they are never encoded.
Perform the following local-change:
Use the Property-Set-XML instead of Property-Set.
Published July 23, 2018 - 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.