XML Deserialization of Result Map Fails 5.4.0.Beta1
tcharman Oct 24, 2012 10:55 AMWe are getting this exception:
16:12:52,091 ERROR [com.irdeto.taskhandler.AbstractTaskHandler] (pool-13-thread-1) An exception occurred downstream of task ConfigurationTaskHandler: Configuration. This likely occurred in a script task or gateway.: com.thoughtworks.xstream.io.StreamException: : only whitespace content allowed before start tag and not h (position: START_DOCUMENT seen h... @1:1)
at com.thoughtworks.xstream.io.xml.XppReader.pullNextEvent(XppReader.java:124) [xstream-1.4.1.jar:]
at com.thoughtworks.xstream.io.xml.AbstractPullReader.readRealEvent(AbstractPullReader.java:148) [xstream-1.4.1.jar:]
at com.thoughtworks.xstream.io.xml.AbstractPullReader.readEvent(AbstractPullReader.java:141) [xstream-1.4.1.jar:]
at com.thoughtworks.xstream.io.xml.AbstractPullReader.move(AbstractPullReader.java:118) [xstream-1.4.1.jar:]
at com.thoughtworks.xstream.io.xml.AbstractPullReader.moveDown(AbstractPullReader.java:103) [xstream-1.4.1.jar:]
at com.thoughtworks.xstream.io.xml.XppReader.<init>(XppReader.java:63) [xstream-1.4.1.jar:]
at com.thoughtworks.xstream.io.xml.AbstractXppDriver.createReader(AbstractXppDriver.java:58) [xstream-1.4.1.jar:]
at com.thoughtworks.xstream.XStream.fromXML(XStream.java:895) [xstream-1.4.1.jar:]
at com.thoughtworks.xstream.XStream.fromXML(XStream.java:886) [xstream-1.4.1.jar:]
at org.drools.process.core.datatype.impl.type.ObjectDataType.readValue(ObjectDataType.java:77) [drools-core-5.5.0.Beta1.jar:5.5.0.Beta1]
at org.jbpm.workflow.instance.node.WorkItemNodeInstance.triggerCompleted(WorkItemNodeInstance.java:223) [jbpm-flow-5.4.0-20120925.045710-447.jar:5.4.0-SNAPSHOT]
at org.jbpm.workflow.instance.node.WorkItemNodeInstance.workItemCompleted(WorkItemNodeInstance.java:309) [jbpm-flow-5.4.0-20120925.045710-447.jar:5.4.0-SNAPSHOT]
This is failing when jbpm-flow tries to deserialize the result map data on completing a task. Some of the values we are mapping are URLs, e.g. "http..." so I'm guessing that's where the "h" comes from in the exception.
This worked in an earlier version of jbpm 5.4.0-SNAPSHOT....
Any help much appreciated.