I am using Camel 2.6.0 with the camel-cache component. I have noticed that Camel is throwing a NullPointerException if a message is sent to a camel-cache endpoint, having body set to null.
This makes sense for operations such as ADD, where the input message body is used as a value, but not really for operations such as DELETE_ALL or GET, where the input message body is not used. In these cases, a setBody must be forced to avoid NPEs being thrown by the camel-cache component. Is this behaviour by design or should it be considered a bug? Thanks Alberto -- View this message in context: http://camel.465427.n5.nabble.com/camel-cache-NPE-for-operations-not-requiring-key-tp4549468p4549468.html Sent from the Camel - Users mailing list archive at Nabble.com.
