[
https://issues.apache.org/jira/browse/CAMEL-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163549#comment-13163549
]
Bilgin Ibryam commented on CAMEL-4300:
--------------------------------------
Hi Piotr,
a late congrats on becoming father :-)
I agree with you that using the same key for the cache doesn't make much sense,
but consistency among all these components is also important. By specifying
statically the operation and the key in the URI you actually specify only the
default values, and you can always override them using the message header. For
example in the URI you could specify only the operation, and use message header
for the key only if it is needed.
> 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
