[jira] Issue Comment Edited: (HIVEMIND-179) Provide access to the Registry

["James Carman (JIRA)" <hi...@jakarta.apache.org>]

    [ https://issues.apache.org/jira/browse/HIVEMIND-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597798#action_12597798 ] 

jwcarman edited comment on HIVEMIND-179 at 5/18/08 4:30 AM:
----------------------------------------------------------------

My point was that the Module can probably get you what you need.  You can lookup services/configurations via the Module itself.  So, you don't need the registry at all.

And, I vote -1 to adding the Registry as a service inside itself.  That just seems way too hacky (as you pointed out) to me.

      was (Author: jwcarman):
    My point was that the Module can probably get you what you need.  You can lookup services/configurations via the Module itself.  So, you don't need the registry at all.
  
> Provide access to the Registry
> ------------------------------
>
>                 Key: HIVEMIND-179
>                 URL: https://issues.apache.org/jira/browse/HIVEMIND-179
>             Project: HiveMind
>          Issue Type: New Feature
>          Components: framework
>            Reporter: Martin Strand
>         Attachments: HIVEMIND-179.txt
>
>
> There is currently no way for a service to access its own Registry.
> This would be useful sometimes, for example if you've got a listener that is invoked from a non-Hivemind thread:
> public class MyService()
> {
>    private Registry registry;
>    public MyService()
>    {
>      registry = getRegistry(); // <-- Need this
>      OutsideHivemind.registerListener(this);
>    }
>    public void invokeListener()
>    {
>      registry.setupThread();
>      // Use some Hivemind services...
>      registry.cleanupThread();
>    }
> }

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