camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Franz Forsthofer (JIRA)" <>
Subject [jira] [Commented] (CAMEL-6339) XML Signature Component in camel/components/xmlsecurity
Date Fri, 23 Aug 2013 12:19:52 GMT


Franz Forsthofer commented on CAMEL-6339:

On second thought to my last comment, probably the best way would be to check if santuario
is available. If santurio is not available then one can use the JDK provider.
> XML Signature Component in camel/components/xmlsecurity
> -------------------------------------------------------
>                 Key: CAMEL-6339
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Franz Forsthofer
>             Fix For: 2.12.0
>         Attachments: CamelComponentXmlsecurity.html, CamelComponentXmlsecurityImproved.html,
ExampleDetached.xml, ExampleEnvelopedXmlSig.xml, ExampleEnvelopingDigSigTampered.xml, ExampleEnvelopingDigSigWithSeveralElementsWithNameRoot.xml,
ExampleEnvelopingDigSig.xml, keystore.jks, ManifestTest_TamperedContent.xml, patch_file_improved2.txt,
patch_file_improved.txt, patch_file.txt, SpringXmlSignatureTests.xml,,
xslt_test.xsl, xslt_test.xsl
> Hello, 
> I have created a component for XML signature. I put it into the component xmlsecurity.
The component has the name xmlsecurity. In the attachments you will find path_file.txt and
CamelComponentxmlsecurity.html. The html file contains a description of the endpoint uris.
> Regards Franz
> ---------------------
> Franz Forsthofer
> e-mail:

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message