[
https://issues.apache.org/jira/browse/CAMEL-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145714#comment-13145714
]
Piotr Klimczak commented on CAMEL-4300:
---------------------------------------
Let`s talk about usability.
For better understanding please take a look at below example:
RouteBuilder builder = new RouteBuilder() { public void configure() {
from("direct:start") .setHeader(CacheConstants.CACHE_OPERATION,
constant(CacheConstants.CACHE_OPERATION_ADD))
.setHeader(CacheConstants.CACHE_KEY, constant("Ralph_Waldo_Emerson"))
.to("cache://TestCache1") } };
In this example the cache key is static. It means that every message will be
added to the cache with same key. In other words there will always be only one
thing in the cache- the last added message.
Believe me you do not want this.
In my opinion this situation will cause any cache absolutely unusable.
I am using this component for some time and every each time i am using it
altogether with simple language
> camel-cache - Make it possible to specify cache operation / key in endpoint
> uri
> -------------------------------------------------------------------------------
>
> Key: CAMEL-4300
> URL: https://issues.apache.org/jira/browse/CAMEL-4300
> Project: Camel
> Issue Type: Improvement
> Components: camel-cache
> Affects Versions: 2.8.0
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 2.9.0
>
> Attachments: camel-cache.uri-config-imp.patch
>
>
> Currently you need to provide headers with an operation and key. Instead it
> should be simpler to do in the uri directly
> .to("cache:myCache?operation=update&key=foo");
> But if there is any headers, then they should take precedence. This is the
> normal convention with other Camel components. That headers takes precedence
> over uri configuration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
