You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (Commented) (JIRA)" <ji...@apache.org> on 2011/11/07 08:23:51 UTC
[jira] [Commented] (CAMEL-4300) camel-cache - Make it possible to
specify cache operation / key in endpoint uri
[ https://issues.apache.org/jira/browse/CAMEL-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13145261#comment-13145261 ]
Claus Ibsen commented on CAMEL-4300:
------------------------------------
The other components dont use simple language in the key name. I think we should make it consistent. And I cannot see a use case where you want this.
> 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