You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "David Bosschaert (JIRA)" <ji...@apache.org> on 2009/11/26 15:13:39 UTC

[jira] Commented: (ZOOKEEPER-584) ZooKeeper service instance should be registered in the OSGi registry

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782905#action_12782905 ] 

David Bosschaert commented on ZOOKEEPER-584:
--------------------------------------------

Yeah, what you'd really want is an OSGi bundle that launches the Zookeeper Service from within the OSGi Framework. It should be configurable through the OSGi Configuration Admin Service and support changes in configuration after the server was launched.

An initial attempt to provide some of this functionality has already been done in the context of ZOOKEEPER-425. Look at the Activator.java and ManagedService.java of [zk_patch3.patch|https://issues.apache.org/jira/secure/attachment/12425484/zk_patch3.patch] in that bug. 

> ZooKeeper service instance should be registered in the OSGi registry
> --------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-584
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-584
>             Project: Zookeeper
>          Issue Type: New Feature
>          Components: server
>            Reporter: Alan Cabrera
>
> When Zookeeper is booted in an OSGi framework by {{ManagedService}} it would be quite handy to have {{ManagedService}} register a management interface for that ZooKeeper instance into the OSGi service registry.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.