camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CAMEL-9498) Always provide a writable local registry
Date Thu, 14 Jan 2016 20:02:40 GMT


ASF GitHub Bot commented on CAMEL-9498:

GitHub user yuruki opened a pull request:

    CAMEL-9498: Always provide a writable local registry (camel-2.16.x)
    plus some polish

You can merge this pull request into a Git repository by running:

    $ git pull camel-9498-2.16

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #773
commit b750650f4482c90995d0d8887c2c4c08d7ce1e2e
Author: Jyrki Ruuskanen <>
Date:   2016-01-10T19:57:15Z

    CAMEL-9498: Always provide a writable local registry

commit 96f991aa312e69838c36dc46915d85abf280c552
Author: Jyrki Ruuskanen <>
Date:   2016-01-12T08:40:21Z

    Local registry example in archetype


> Always provide a writable local registry
> ----------------------------------------
>                 Key: CAMEL-9498
>                 URL:
>             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
> 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

View raw message