Thanks for suggestion, I have placed a JSON validator in place for now.
Please let me know when this fix will be available.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-MongoDB-Bug-related-to-Type-Conversion-tp5746090p5746095.html
Sent from the Camel - Users mailing
Hello,
Yes, as far as I remember the Type Converter Registry memorises what
converters were successful in converting from a given source to a
destination type, with the goal of speeding up the resolution of future
type conversion attempts. Probably this converter is getting blacklisted
due to the
t(DBApiLayer.java:384)
at com.mongodb.DBApiLayer$Result.next(DBApiLayer.java:346)
at com.mongodb.DBCursor._next(DBCursor.java:421)
Camel version is 2.12.1 and mongodb is 2.4. Please tell me if there is
something wrong in my implementation because this is causing problems in my
web application. I cannot afford to restart the server again and again if
someone tries with some bad input :)
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-MongoDB-Bug-related-to-Type-Conversion-tp5746090.html
Sent from the Camel - Users mailing list archive at Nabble.com.
