camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-9498) Always provide a writable local registry
Date Sat, 16 Jan 2016 12:04:39 GMT

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

Claus Ibsen commented on CAMEL-9498:
------------------------------------

Yeah I can see the point of being able to run osgi unit tests without the real osgi container.


We can ponder a bit more about whether to introduce a LocalRegistry concept for camel-test
modules, to allow to add/override beans in the registry from an unit test, in the unit test
code. If so I think a general api in camel-test should be introduced that all the testing
components can rely upon. 
Then camel-scr can adapt and use that too. Maybe we need a camel-test-scr module?

> 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