Totally agree.

- Romain

Le 23 mai 2011 17:50, "Charles Moulliard" <cmoulli...@gmail.com> a écrit :
> Hi Romain,
>
> Just a quick thought about what you call camel-codec but doing hasing
> of a file using MD5 algorithm. As this is part of crypto concern, we
> should integrate your code into the following existing component
> (http://camel.apache.org/crypto-digital-signatures.html) and not
> creating a new one
>
> crypto:sign
> crypto:verify
> --> crypto:digest
>
> Regards,
>
> Charles Moulliard
>
> Sr. Principal Solution Architect - FuseSource
> Apache Committer
>
> Blog : http://cmoulliard.blogspot.com
> Twitter : http://twitter.com/cmoulliard
> Linkedin : http://www.linkedin.com/in/charlesmoulliard
> Skype: cmoulliard
>
>
>
> On Mon, May 23, 2011 at 5:27 PM, Romain Manni-Bucau
> <rmannibu...@gmail.com> wrote:
>> Hi,
>>
>> i wrote 2 camel components,
>>
>> - the first one is very simple and could be a language: camel-assert (
>> http://code.google.com/p/rmannibucau/source/browse/camel/camel-assert/):
it
>> just allow to check values in a route, i know i could have used simple
but i
>> wanted something more close to junit Assert class and really more simple
>> than what is dont to evaluate a language expression.
>>
>> from("direct:arrayEquals").to("assert:equals").to("mock:arrayEquals");
>>
>> template.sendBodyAndHeader("direct:arrayEquals", new String[] { "a",
>> "b" }, AssertComponent.ACTUAL_HEADER_KEY, new String[] { "a", "b" });
>>
>>
>> - the second one is simple too but can be useful when you work with
files:
>> camel-codec (
>>
http://code.google.com/p/rmannibucau/source/browse/camel/#camel%2Fcamel-codec
),
>> it allows to create hashes from a file.
>>
>> from("direct:start").to("codec:MD5").to("mock:result");
>>
>> sendBody("direct:start",
>> getClass().getClassLoader().getResourceAsStream("foo.txt"));
>> Of course both can be used together to check a file ckecksum.
>>
>> Any thought about it? I created jira about them.
>>
>> - Romain
>>

Reply via email to