[
https://issues.apache.org/activemq/browse/CAMEL-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58391#action_58391
]
Claus Ibsen commented on CAMEL-2482:
------------------------------------
trunk: 926499.
I have to polish it a bit
- fixed spellings
- fixed pom.xml to be a bundle
- renamed a long constant in Constants
- added it to the dist kit
I have two suggestions
- I think the {{sign}} and {{verify}} components should be one component
{{crypto}} and then you specify a mode instead,
eg {{.to("crypto:sign://provider?privateKey=myPrivateKey&provider=SUN"}}
Then there is only one component scheme to remember. And if we get something
in the future that might clash with sign/verify then we avoid this issue having
crypto as the grand scheme name
- I wonder if bouncy-castle .jar can be set to test scope as its not imported
in java code, and you are supposed to install a JSSE provider yourself.
Stephen your thoughts?
> camel-bouncycastle - A new component for crypto
> -----------------------------------------------
>
> Key: CAMEL-2482
> URL: https://issues.apache.org/activemq/browse/CAMEL-2482
> Project: Apache Camel
> Issue Type: New Feature
> Reporter: Claus Ibsen
> Assignee: Stephen Gargan
> Fix For: 2.3.0
>
> Attachments: camel-crypto.patch, core-crypto-dataformat.patch,
> parent.patch
>
>
> See more at:
> http://www.bouncycastle.org/
> Basically a Camel DataFormat that leverages bouncycastle would be good.
> Its using a MIT/X11 license which should be friendly with Apache
> http://bouncycastle.org/licence.html
> http://www.apache.org/legal/3party.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
