camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ulrich Merckx (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CAMEL-3771) The body of an exchange should not be required when not performing an add or update to the cache
Date Wed, 09 Mar 2011 11:02:00 GMT

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

Ulrich Merckx updated CAMEL-3771:
---------------------------------

    Attachment: Removed_necessity_for_a_not_null_body_when_doing_actions_where_the_body_is_not_used.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
>         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

Mime
View raw message