The following comment has been added to this issue:

     Author: James Carman
    Created: Fri, 25 Jun 2004 10:19 AM
       Body:
The problem with requiring that a service be declared to "handle" all 
contributions to a configuration is that maybe you don't really WANT to have 
another service out there in the registry available to everyone.  All you 
really need to do is some initialization logic to do something with those 
contributions once they're registered.  Maybe come up with a 
ConfigurationManager interface...

public interface ConfigurationManager
{
  public void setContributions( Collection contributions );
}  

That way, it's not a real "service", but it is instantiated and managed by 
HiveMind.  Does that sound reasonable?  Am I way off here?

p.s.  I didn't know if this is the correct place for discussing something like 
this or not.  There is no mailing list for HiveMind yet (at least I couldn't 
find it), but I wanted to get some feedback on the idea.
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/HIVEMIND-11?page=comments#action_36352

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/HIVEMIND-11

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HIVEMIND-11
    Summary: getConfiguration missing from Registry Interface
       Type: Bug

     Status: Open
   Priority: Major

    Project: HiveMind
 Components: 
             framework
   Versions:
             1.0

   Assignee: Howard M. Lewis Ship
   Reporter: Achim H�gen

    Created: Fri, 25 Jun 2004 2:02 AM
    Updated: Fri, 25 Jun 2004 10:19 AM

Description:
The getConfiguration method is no longer present in the registry interface but 
has been moved to RegistryInfrastructure.
That change made dealing with the registry unintuitive, retrieving a 
configuration requires some good guesswork, especially since the documentation 
is not uptodate.

Let's have a look how the documentation must change, this reveals some of the 
difficulties. Current documentation:

Registry registry = . . .;
List elements = registry.getConfiguration("com.myco.MyConfig"); 

Simple and clean. Instead we need a reference to RegistryInfrastructure. 
Only solution is a cast:

List elements = ( (RegistryInfrastructure) registry 
).getConfiguration("com.myco.MyConfig");    

Besides beeing unintuitive, there is no contract, that ensures that the 
Registry object additionally implements RegistryInfrastructure!
IMHO, dealing with two different interfaces for the most basic tasks is no good 
idea.
Howard, you already admitted on the mailing list, that you 'probably have been 
overly zealous in removing getConfiguration()'
Please restore the method.

Achim Huegen




---------------------------------------------------------------------
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]

Reply via email to