[ 
http://issues.apache.org/jira/browse/HIVEMIND-111?page=comments#action_64047 ]
     
Knut Wannheden commented on HIVEMIND-111:
-----------------------------------------

The hivemind.Startup configuration is used by the hivemind.Startup service to 
bootstrap HiveMind.  A hivemind.Startup contribution (i.e. a Runnable object) 
can perform arbitrary actions and will be run just after all services and 
configurations have been defined, but before the Registry is returned to the 
client, to "bootstrap" the Registry.  HiveMind itself only contributes the 
hivemind.EagerLoad service (with the corresponding hivemind.EagerLoad 
configuration) to hivemind.Startup.

The Runnable interface is used here because it's a standard interface and 
fulfills all needs.  It doesn't make much sense for HiveMind to define its own 
for this purpose.

All hivemind.Startup contributions must be run before the Registry is returned 
to the client.  Thus even if the contributions were executed asynchronously the 
hivemind.Startup service would have to wait for all of them to yield.

Do you have any specific needs for running hivemind.Startup contributions in 
parallel?  Could you provide a use case?

> StartupImpl.java - not starting a thread
> ----------------------------------------
>
>          Key: HIVEMIND-111
>          URL: http://issues.apache.org/jira/browse/HIVEMIND-111
>      Project: HiveMind
>         Type: Bug
>   Components: framework
>     Versions: 1.1
>     Reporter: Tomas Knappek

>
> Class org.apache.hivemind.impl.StartupImpl contains the command r.run() on 
> line 38, I think it should be r.start() because the current implemention just 
> run the method "run"   instead of starting new thread. Otherwise I don't see 
> any point to use the Runnable interface.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to