Handling of Invalid XML

When the payload runs, SSC validates the overall structure of the input payload. In the case of catastrophic errors, the entire input payload is rejected.

SAXParser (a third party product used by SSC) then validates the structure of each payload record immediately before processing. If SAXParser detects a formatting error, it returns the error details to SSC, which wraps them and returns them in a string in the following format:

com.systemsunion.SSTS.exec.MethodExecutionException

The following error occurred - 'org.xml.sax.SAXParseException: XML document structures must start and end within the same entity.'

or

com.systemsunion.SSTS.exec.MethodExecutionException

The following error occurred - 'org.xml.sax.SAXParseException: The element type "AccountCode" must be terminated by the matching end-tag "</AccountCode>".'

If your payload fails with a SAXParser error, this indicates that your input payload XML elements are incorrectly formatted and SSC cannot process them.

Opening your payload in an XML-aware editor such as XMLSpy can readily highlight the offending lines, as can opening the payload in Microsoft Internet Explorer (although the error reporting features are more basic).

The following table lists some of the commonly encountered reasons for formatting errors: