camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-3846) Registry - Add support for filtering based on registry type / ordering to lookup
Date Sun, 10 Jul 2011 08:46:00 GMT

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

Claus Ibsen updated CAMEL-3846:
-------------------------------

    Fix Version/s: 3.0.0
         Assignee:     (was: Claus Ibsen)

> Registry - Add support for filtering based on registry type / ordering to lookup
> --------------------------------------------------------------------------------
>
>                 Key: CAMEL-3846
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3846
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core
>    Affects Versions: 2.7.0
>            Reporter: Claus Ibsen
>             Fix For: 3.0.0
>
>
> When you have multiple registry to lookup resources, it would be great if end users can
specify which registry (by a logical name / type) to be used. And maybe an ordering as well.
> If people use a custom registry, they may want to indicate that Camel should only lookup
in that registry.
> <from uri="myEndpoint?registryName=db"/>
> For example to lookup by key: myEndpoint from a custom registry with the name: db
> <from uri="myEndpoint?registryName=db,*"/>
> To lookup in DB first, and then fallback to the default registries
> <from uri="myEndpoint?registryName=db,spring"/>
> To lookup in DB first, and then Spring afterwards
> This requires an API change in Registry so it can indicate its name.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message