[
https://issues.apache.org/jira/browse/CAMEL-11252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004239#comment-16004239
]
Luca Burgazzoli commented on CAMEL-11252:
-----------------------------------------
The intention was to add more flexibility to the camel context as follow up for
having a way to atomically add a service if not already registered raised
during camel-reactive-streams development but yeah, something can be added in
CamelContextHelper for 2.x and introduced in the CamelContext API in 3.0.
Maybe in the 3.0 the CamelContext could use the "Predicate way" by default and
the CamelContextHelper could then provide helpers to find by id, find by type
so that we can keep the API limited and we can provide a number of helper
functions when new needs arise.
Would that make any sense ?
> camel-core : allow to retrieve components/endpoints/etc list with a predicate
> -----------------------------------------------------------------------------
>
> Key: CAMEL-11252
> URL: https://issues.apache.org/jira/browse/CAMEL-11252
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Luca Burgazzoli
> Assignee: Luca Burgazzoli
> Priority: Minor
> Fix For: 2.20.0
>
>
> As today components/endpoints and so on can be retrieved/removed from the
> camel context by id but it would be nice to have a more flexible way to
> retrieve them like:
> {code:java}
> List<Component> components = context.getComponents(id, component -> {
> return component instanceof IdAware;
> });
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
