We did some changes try with latest source code
On Tue, Oct 1, 2013 at 6:55 PM, atiato wrote:
> Hi Claus ,
>
> I didn't get any reply for this ? should we open this as JIRA ?
>
> thanks,
> Omar Atia
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/contentObjectId-in
Hi Claus ,
I didn't get any reply for this ? should we open this as JIRA ?
thanks,
Omar Atia
--
View this message in context:
http://camel.465427.n5.nabble.com/contentObjectId-in-XML-Security-camel-xmlsecurity-tp5740265p5740707.html
Sent from the Camel - Users mailing list archive at Nabble.
Dear Claus ,
Please check the above error message when setting the camel header for
Content reference URI ?
thanks,
Omar Atia
--
View this message in context:
http://camel.465427.n5.nabble.com/contentObjectId-in-XML-Security-camel-xmlsecurity-tp5740265p5740536.html
Sent from the Camel - Users
Dear Claus ,
What about this error when setting the header to change Reference URI ?
#Body
it raises the following exception :
org.apache.camel.component.xmlsecurity.api.XmlSignatureException:
javax.xml.crypto.dsig.XMLSignatureExce
Hi
Yeah some setters is missing on this. I have logged a ticket
https://issues.apache.org/jira/browse/CAMEL-6796
On Sat, Sep 28, 2013 at 12:20 PM, atiato wrote:
> Dear Clause,,
>
> it raises the below error when using small letter.
>
>
> uri="xmlsecurity:sign://enveloped?keyAccessor=#accessorRs
Dear Clause,,
it raises the below error when using small letter.
pom.xml :
org.apache.camel
camel-xmlsecurity
${camel.version}
2.12.1
I think we have to Open JIRA for this and for the error when when setting
the header CamelXmlSignatureContentRefe
I will try again in small letter and get back to you ...I remember I did both
and it didn't work .
--
View this message in context:
http://camel.465427.n5.nabble.com/contentObjectId-in-XML-Security-camel-xmlsecurity-tp5740265p5740346.html
Sent from the Camel - Users mailing list archive at Nabb
The first letter should be in lower case, eg
ContentObjectId=Body
should be
contentObjectId=Body
On Fri, Sep 27, 2013 at 1:25 PM, atiato wrote:
> Dears Claus,
>
> the solution is as below when specifying the header
> CamelXmlSignatureContentReferenceUri with #Body , it raises the above
> excep
I added the following :
#Body
it raises the following exception :
org.apache.camel.component.xmlsecurity.api.XmlSignatureException:
javax.xml.crypto.dsig.XMLSignatureException:
javax.xml.crypto.URIReferenceException:
org.apache.xml
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
contentObjectId is used to change the reference URI and apply it during
signing of the message .
Well I want to sign XML message using camel-xmlsecurity and I have change
the code for this component to Sign the message .
the Question should I open JIRA for the exception when using the Header of
C
What is "contentObjectId"? What do you want to achieve?
Colm.
On Thu, Sep 26, 2013 at 5:54 PM, atiato wrote:
> Dears ,
>
> Please let me know how to fill contentObjectId when signing XML messages.
>
> Please example I already searched github and sources and didn't have the
> luck to find any
12 matches
Mail list logo
