camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-10127) OsgiDefaultCamelContext should call parent constructor with registry
Date Wed, 06 Jul 2016 10:03:10 GMT

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

ASF GitHub Bot commented on CAMEL-10127:
----------------------------------------

GitHub user borcsokj opened a pull request:

    https://github.com/apache/camel/pull/1067

    CAMEL-10127: call parent constructor of OsgiDefaultCamelContext with registry

    calling super with registry or a new OsgiServiceRegistry if not specified

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

    $ git pull https://github.com/borcsokj/camel master

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

    https://github.com/apache/camel/pull/1067.patch

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

    This closes #1067
    
----
commit ac5a57bd3181d0d2be8a83cc9bcec17ecd637136
Author: Börcsök József <borcsokj@sch.bme.hu>
Date:   2016-07-06T09:59:15Z

    CAMEL-10127: call parent constructor of OsgiDefaultCamelContext with registry

----


> OsgiDefaultCamelContext should call parent constructor with registry
> --------------------------------------------------------------------
>
>                 Key: CAMEL-10127
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10127
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-osgi
>    Affects Versions: 2.17.1
>            Reporter: Börcsök József
>
> OsgiDefaultCamelContext constructor doesn't call super to pass registry so inconsistent
registries are set in DefaultCamelContext and DefaultCamelContext instances.
> If a client create OsgiDefaultCamelContext with custom registry then (private) variable
in DefaultCamelContext is not initialized and a different new instance will be created by
getRegistry method.
> Either scope of registry in DefaultCamelContext should be changed to protected or OsgiDefaultCamelContext
should pass the reference.



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

Mime
View raw message