[
https://issues.apache.org/jira/browse/HIVEMIND-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12596881#action_12596881
]
James Carman commented on HIVEMIND-179:
---------------------------------------
I believe it would be available. The service implementation factory can get a
handle on the registry when the service is asked for. Remember, HiveMind
doesn't like to create what it doesn't have to, so the actual implementation
isn't created until absolutely necessary (i.e. a method is invoked upon it).
This would probably even work for primitive service models.
> 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
>
> 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.
