[
https://issues.apache.org/jira/browse/CAMEL-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108501#comment-13108501
]
Piotr Klimczak commented on CAMEL-4300:
---------------------------------------
Sorry for leaving this improvement w/o answer.
Unfortunately I did not have a chance to start programming yet. This is because
I became a happy father much earlier than I thought (few weeks) and because of
that I am doing much repairs in my flat.
This is also the very first moment when i have turned on my PC since last few
weeks.
For now I am not sure when I will be able to start programming (maybe at the
beginning of October).
Please don't get me wrong- I do really want to make this improvement as since
my last changes I feel a kind of "owner" of cache component. But I'm not free
enough to do it now.
Hope you don't mind.
> 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
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
