[
https://issues.apache.org/jira/browse/CAMEL-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145719#comment-13145719
]
Piotr Klimczak commented on CAMEL-4300:
---------------------------------------
sorry for multiple comments i am using my tablet.
So the usual usage of camel cache component is:
RouteBuilder builder = new RouteBuilder() { public void configure() {
from("direct:start") .setHeader(CacheConstants.CACHE_OPERATION,
constant(CacheConstants.CACHE_OPERATION_ADD))
.setHeader(CacheConstants.CACHE_KEY, simple("body.id"))
.to("cache://TestCache1") } };
This is equal to: to("cache://TestCache1? operation=add&key=${body.id}").
I just cannot imagine usability of this component w/o simple language or any
other, as the CA he key must be dynamic and is always in body or set as a
header of message.
Please let me know if i made you to change your mind.
Greetings,
Piotr Klimczak
> 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
