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

Service Soap Throws Exception while parsing



Service Soap fails to parse "&" and "<". Special Characters "<" and "&" in Employer Name field under incoming Request is not accepted by schema and throws error .

Error Messages

2015-06-18 09:06:39,886 [fault (self-tuning)'] [ STANDARD] [ ] ( mapping.xml.XMLParserBase) ERROR user01|xx.xx.xx.xx - Caught exception parsing XML stream
org.xml.sax.SAXParseException: The reference to entity "BC" must end with the ';' delimiter.

Steps to Reproduce

In the incoming XML, pass "&" or "<" in the Request.

Root Cause

In XML, '&' is a special character. It's used to represent "entities" such as <. And for the '<' character which is also a special character). So for  'H&R' intends  to be an entity like 'H&R;' - entities one must end it in a semi-colon.


To include a plain ampersand character '&', replace it with '&amp;'

<ces:employer-name>H&R Block</ces:employer-name>

<ces:employer-name>H&ampR Block</ces:employer-name>


Published July 29, 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