[ https://issues.jboss.org/browse/DROOLS-3075?page=com.atlassian.jira.plugi... ] Geoffrey De Smet updated DROOLS-3075: ------------------------------------- Description: Currently kie-server only supports XPath references in XStream. Add a http parameter to make kie-server's XStream marshaller call: {code} xStream.setMode(XStream.ID_REFERENCES); {code} Motivation by community user: It's very usefull for projects developed via kie-wb to set XStream mode (ID or ID_REFERENCES) similar to how there's a http parameter to switch between xstream xml, jaxb xml and jackson json. Actually when submit to kie-server an xml body to post for solution (optaplanner feature) an error *com.thoughtworks.xstream.converters.ConversionException: Invalid reference* is raised by kie-server, if the xml have reference to facts using id's instead of XPath. XML with XPath reference is very hard to read for users and to produce dinamically for app that post/get xml data via rest api. was: Currently kie-server only supports XPath references in XStream. Add a http parameter to make kie-server's XStream marshaller call: {code} xStream.setMode(XStream.ID_REFERENCES); {code} Motivation: It's very usefull for projects developed via kie-wb to set XStream mode (ID or ID_REFERENCES) similar to how there's a http parameter to switch between xstream xml, jaxb xml and jackson json. Actually when submit to kie-server an xml body to post for solution (optaplanner feature) an error *com.thoughtworks.xstream.converters.ConversionException: Invalid reference* is raised by kie-server, if the xml have reference to facts using id's instead of XPath. XML with XPath reference is very hard to read for users and to produce dinamically for app that post/get xml data via rest api. -- This message was sent by Atlassian Jira (v7.12.1#712002)