camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CAMEL-4300) camel-cache - Make it possible to specify cache operation / key in endpoint uri
Date Mon, 12 Mar 2012 10:08:37 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen resolved CAMEL-4300.
--------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.9.2)
         Assignee: Claus Ibsen

Thanks for the patch. I updated the cache wiki page with the 2 new endpoint options.
                
> 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
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.10.0
>
>         Attachments: camel-cache.uri-config-imp.patch, camelCacheUrlOpts.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

        

Mime
View raw message