Dears Claus, the solution is as below when specifying the header CamelXmlSignatureContentReferenceUri with #Body , it raises the above exception , so as a work around we were unable to add the ContentObjectId to uri when signing because it has no setter method inside the camel-xmlsecurity jar file , so as an action download sources compiling and adding the setter in order to make it as option or parameter to signing uri as below :
<to uri="xmlsecurity:sign://enveloped?keyAccessor=#accessorRsa&addKeyInfoReference=true&transformMethods=#NoCommTrans&ContentObjectId=Body" /> camel-context.xml <http://camel.465427.n5.nabble.com/file/n5740288/camel-context.xml> XmlSignerConfiguration.java <http://camel.465427.n5.nabble.com/file/n5740288/XmlSignerConfiguration.java> public void setContentObjectId(String contentObjectId) { this.contentObjectId = contentObjectId; } let me know if I have to open a JIRA for this issue . thanks, Omar Atia -- View this message in context: http://camel.465427.n5.nabble.com/contentObjectId-in-XML-Security-camel-xmlsecurity-tp5740265p5740288.html Sent from the Camel - Users mailing list archive at Nabble.com.