Hi Claus!
Please take a look at my last comment [1] to see if it makes sense to you.
[1] https://issues.apache.org/jira/browse/CAMEL-4959
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/ObjectConverter-problem-tp5517376p5521526.html
Sent from the Camel Development mail
Hi
Yeah this is correct. I am adding a special check for NaN in the type
converter so we can deal with this situation.
On Sun, Feb 26, 2012 at 10:58 PM, michal.warecki
wrote:
> Hmm, looks like more to work around the problem by changing the test instead
> of improving the code :-) There is no I
Hmm, looks like more to work around the problem by changing the test instead
of improving the code :-) There is no Integer equivalent to Double.NaN and
Float.NaN so it seems more appropriate to me to return null value. It seems
to me that this should be treated like the rest of the types that have
Hi
Thanks for spotting this and indeed I do agree on this with you which IMHO
is a regression failure introduced by [1], but first let's see what
Christian's idea was [2] to change the unit-test instead of fixing
ObjectConverter itself.
[1] https://issues.apache.org/jira/browse/CAMEL-4959
[2] ht
