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 no Integer equivalent.
The case is currently implemented whenever xpath does not find value, returns 0 which is not correct. Cheers -- View this message in context: http://camel.465427.n5.nabble.com/ObjectConverter-problem-tp5517376p5517571.html Sent from the Camel Development mailing list archive at Nabble.com.
