[jira] Resolved: (CAMEL-3771) The body of an exchange should not be required when not performing an add or update to the cache

["Claus Ibsen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-3771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-3771.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.7.0

trunk: 1079749.

Thanks for the patch.

> The body of an exchange should not be required when not performing an add or update to the cache
> ------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-3771
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3771
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-cache
>    Affects Versions: 2.3.0
>            Reporter: Ulrich Merckx
>            Assignee: Claus Ibsen
>             Fix For: 2.7.0
>
>         Attachments: Removed_necessity_for_a_not_null_body_when_doing_actions_where_the_body_is_not_used.patch
>
>
> When not performing an add or update to the cache, the body of the exchange should of no matter and should be nullable. 
> At the moment this is not possible when for example performing an operation such as get. It is now required to pass for example an empty string in the body of the exchange, which is kind of useless.
> The attached patch implements the altered behaviour where the body may be nullable when not performing add or update. A CacheException will be thrown when the body is required for an operation but the content of the body is null. 
> The patch contains the patched CacheProducer and the tests in CacheProducerTest.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira