The following issue has been updated:
Updater: Christian Domsch (mailto:[EMAIL PROTECTED])
Date: Fri, 25 Jun 2004 6:35 AM
Comment:
The contents of the zipfile are a small eclipse project that demonstrates the
problem. To be able to run the main class, the run-configuration inside eclipse
must include the main directory, the adder directory and the adder-impl
directory so that hivemind can find all sdl files and log4j gets the xml config
file.
Changes:
Attachment changed to hivemind.zip
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/HIVEMIND-13?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/HIVEMIND-13
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HIVEMIND-13
Summary: core services implementing RegistryShutdownListener do not receive
shutdown event
Type: Bug
Status: Unassigned
Priority: Major
Project: HiveMind
Components:
framework
Versions:
1.0
Assignee:
Reporter: Christian Domsch
Created: Fri, 25 Jun 2004 6:31 AM
Updated: Fri, 25 Jun 2004 6:35 AM
Environment: Windows XP, jdk1.5.0 beta2, eclipse 3.0 rc3
Description:
When a core service implementation implements RegistryShutdownListener the
corresponding #registryDidShutdown() method should be called. This does not
happen. I tested for primitive and singleton model. I further stepped through
the code of hivemind and it seems to me, that the problem is somewhere inside
the dynamic class generation. But I cannot tell for sure.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
