camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Piotr Klimczak (Commented) (JIRA)" <>
Subject [jira] [Commented] (CAMEL-4300) camel-cache - Make it possible to specify cache operation / key in endpoint uri
Date Fri, 07 Oct 2011 21:40:30 GMT


Piotr Klimczak commented on CAMEL-4300:

I am thinking about usability of this improvement.
In your example i can see that the key param is static. It makes it quite usable.

So i have decided to use simple language which will make it much more powerfull.

So basic example looks like this: to("cache://TestCache1?operation=add&key=${}").
Nice isn't it?

As i know the url parameters incjection functionality doesn't support "dynamic" values (can
inject only static string). So the simple language functionality can be added with very small
additional code with BaseSimpleParser.

Please tell me what do you think about this Claus? Is that ok to use a simple language in
URLS? Or maybe it will break some compatybility with spring/blueprint or any other thing?

Waiting for your answer. 

> camel-cache - Make it possible to specify cache operation / key in endpoint uri
> -------------------------------------------------------------------------------
>                 Key: CAMEL-4300
>                 URL:
>             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.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message