You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by jephreycuma <je...@gmail.com> on 2017/08/02 14:21:02 UTC
apache camel toD does not accept a property value of about 40
characters
Hi everyone,
I calculated a message digest value using DigestUtils.sha1Hex(String value),
which gave me a long string of about 40 characters (e.g
dd543d3bcb28e577313f8b945f29a9be7a43c5fd).
I needed to pass this messageDigest value to my internal camel component
which in turn is supposed to write it to our DB. To achieve this, I used
<toD uri
="message-history/somevalue/othervalues&messageDigest=dd543d3bcb28e577313f8b945f29a9be7a43c5fd"
/> of camel 2.17.5.
This sent an empty value of messageDigest to my message-history component.
However when I use
<recipientList>
<simple>
message-history/somevalue/othervalues&messageDigest=dd543d3bcb28e577313f8b945f29a9be7a43c5fd
</simple>
</recipientList>
it does send a value of messageDigest to my message-history component, and
also when I make the value of messageDigest smaller say about 5 characters,
the camel toD does send the value of messageDigest.
Could this be a bug in camel 2.17.5 on toD?
--
View this message in context: http://camel.465427.n5.nabble.com/apache-camel-toD-does-not-accept-a-property-value-of-about-40-characters-tp5809139.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: apache camel toD does not accept a property value of about 40 characters
Posted by Claus Ibsen <cl...@gmail.com>.
There is no limit to the length of options in Camel etc, so I would be
surprised if there is a bug in Camel in this regard. I suggest to dive
deeper. And also test this on newer versions of Camel etc if you can
reproduce on a supported branch. 2.17.x is EOL.
On Wed, Aug 2, 2017 at 4:21 PM, jephreycuma <je...@gmail.com> wrote:
> Hi everyone,
> I calculated a message digest value using DigestUtils.sha1Hex(String value),
> which gave me a long string of about 40 characters (e.g
> dd543d3bcb28e577313f8b945f29a9be7a43c5fd).
> I needed to pass this messageDigest value to my internal camel component
> which in turn is supposed to write it to our DB. To achieve this, I used
> <toD uri
> ="message-history/somevalue/othervalues&messageDigest=dd543d3bcb28e577313f8b945f29a9be7a43c5fd"
> /> of camel 2.17.5.
> This sent an empty value of messageDigest to my message-history component.
> However when I use
> <recipientList>
> <simple>
> message-history/somevalue/othervalues&messageDigest=dd543d3bcb28e577313f8b945f29a9be7a43c5fd
> </simple>
> </recipientList>
> it does send a value of messageDigest to my message-history component, and
> also when I make the value of messageDigest smaller say about 5 characters,
> the camel toD does send the value of messageDigest.
> Could this be a bug in camel 2.17.5 on toD?
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/apache-camel-toD-does-not-accept-a-property-value-of-about-40-characters-tp5809139.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2