camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jyrki Ruuskanen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-9498) Always provide a writable local registry
Date Fri, 15 Jan 2016 13:46:39 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-9498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101781#comment-15101781
] 

Jyrki Ruuskanen commented on CAMEL-9498:
----------------------------------------

I would like to add that the PR hardly brings confusion to users since the local registry
is empty by default and only accessible through getLocalRegistry(). Essentially we are just
adding out-of-the-box flexibility.

Making the OSGi service registry easier to write to will be a clear improvement, but it won't
help people like us who like to run complete and complex Camel contexts in JUnit and OSGi
without conditional code and additional setting up.

> 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-scr
>            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. 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message