[
https://issues.apache.org/jira/browse/CAMEL-9498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jyrki Ruuskanen updated CAMEL-9498:
-----------------------------------
Description:
Many Camel components need to reference objects in CamelContext's registry as
part of their configuration (for example httpClientConfigurer for http/http4
and restletRealm for restlet).
These objects often apply to that particular CamelContext and not others, thus
the registry holding these bits could be local instead of, say, OSGi service
registry. Using a local registry prevents the risk of conflicting keys and
spares us from devising a naming policy for even trivial stuff.
To conveniently create and add these objects, even from inside RouteBuilder's
configure method, we need write access to said registry.
CamelContext should, in my opinion, provide a local SimpleRegistry that is
always available.
was:
Many Camel components need to reference objects in CamelContext's registry as
part of their configuration (for example httpClientConfigurer for http/http4
and restletRealm for restlet).
These objects often apply to that particular CamelContext and not others, thus
the registry holding these bits could be local. Using a local registry prevents
the risk of conflicting keys and spares us from devising a naming policy for
even trivial stuff.
To conveniently create and add these objects, even inside RouteBuilder's
configure method, we need write access to said registry.
Component/s: (was: camel-scr)
camel-core
> Always provide a writable local registry
> ----------------------------------------
>
> Key: CAMEL-9498
> URL: https://issues.apache.org/jira/browse/CAMEL-9498
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Jyrki Ruuskanen
> Priority: Minor
>
> Many Camel components need to reference objects in CamelContext's registry as
> part of their configuration (for example httpClientConfigurer for http/http4
> and restletRealm for restlet).
> These objects often apply to that particular CamelContext and not others,
> thus the registry holding these bits could be local instead of, say, OSGi
> service registry. Using a local registry prevents the risk of conflicting
> keys and spares us from devising a naming policy for even trivial stuff.
> To conveniently create and add these objects, even from inside RouteBuilder's
> configure method, we need write access to said registry.
> CamelContext should, in my opinion, provide a local SimpleRegistry that is
> always available.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
