Posts tagged "SAXParseException"

LiveCycle ES: SAXParseException: White spaces are required between publicId and systemId.

Issue

If you have migrated from LiveCycle 7 to LiveCycle ES you may encounter the following exception when attempting to call a web service from an orchestration at runtime:

####<Feb 18, 2010 5:09:56 PM MET> <Warning> <com.adobe.workflow.AWS> <sunc01016> <wl01qalc01> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-56EAC5B49D0141CB0D30> <> <1266509396427> <000000> <ALC-DSC-000-000: com.adobe.idp.dsc.DSCRuntimeException: Internal error. 
...
Caused by: ALC-DSC-000-000: com.adobe.idp.dsc.DSCRuntimeException: Internal error. 
 at com.adobe.idp.dsc.util.CoercionUtil.toDOMDocument(CoercionUtil.java:683) 
 at com.adobe.idp.dsc.util.CoercionUtil.toDOMDocument(CoercionUtil.java:688) 
 at com.adobe.idp.dsc.util.CoercionUtil.toType(CoercionUtil.java:970) 
 at com.adobe.idp.dsc.util.CoercionUtil.toType(CoercionUtil.java:836) 
 at com.adobe.workflow.datatype.runtime.support.AbstractDataTypeRuntimeHandler.coerceFrom(AbstractDataTypeRuntimeHandler.java:64) 
 at com.adobe.workflow.datatype.runtime.support.AbstractComplexDataTypeRuntimeHandler.getNode(AbstractComplexDataTypeRuntimeHandler.java:47) 
 at com.adobe.workflow.dom.VariableElement.setBoundValue(VariableElement.java:98) 
 at com.adobe.workflow.pat.service.PATExecutionContextImpl.setProcessDataValue(PATExecutionContextImpl.java:813) 
 ... 116 more 
Caused by: org.xml.sax.SAXParseException: White spaces are required between publicId and systemId. 
 at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) 
 at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) 
 at com.adobe.idp.dsc.util.DOMUtil.parseDocumentFromString(DOMUtil.java:167) 
 at com.adobe.idp.dsc.util.CoercionUtil.toDOMDocument(CoercionUtil.java:607) 
 ... 123 more

When accessing the web service through the WebService component, you sometimes get a valid response using the test tab:

Solution

The web service is returning an invalid XML result. This error usually happens when the classpath for the server is not correctly set up. Check the classpath against the Adobe documentation, make any necessary changes, and then restart the application server.

In this case, the argument for the UTF-8 charset was not set correctly and therefore the input and output data for the WebService component was not correctly encoded.

reference: (181450296)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle ES: SAXParseException: The processing instruction target matching “[xX][mM][lL]” is not allowed

Issue

 If you are attempting to upgrade a LC7 process in Workbench you may encounter the following error related to a SetValue QPAC:

None (Error finding upgrades: org.xml.sax.SAXParseException: 
The processing instruction target matching "[xX][mM][lL]" is not allowed.)

The SetValue QPAC is not upgraded, but other QPACs are upgraded successfully to LC ES components.

Reason

 The error is caused by the presence of the XML declaration <?xml version=”1.0″ encoding=”iso-8859-1″?> at the start of an XPath value in a SetValue expression.  The upgrade tool cannot handle this XML declaration correctly and throws the error.  If you remove this XML declaration manually before upgrading the process, it will upgrade successfully.

Solution

 This issue is fixed in Workbench ES2.  There is a patch available for LC Workbench ES 8.2.1.2, so you can contact enterprise support if you require this patch.

reference: (181105115/2403177)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)