Re: [higgins-dev] configuration component requirements

[Michael McIntosh <mikemci@xxxxxxxxxx>]

Some additional thoughts...

During the weekly call it was suggested that - in order to support 
management applications - a configurable component should provide a "way" 
to discover its expected/supported configuration settings.

My initial reaction to this was great idea, and that it could be added to 
the interface, something like:

public interface IConfigurableComponent
{ 
        public abstract ISupportedConfigurationDescription 
getSupportedConfiguration();
 
        public abstract void configure
                (java.util.Map mapGlobalSettings,
                String strComponentName,
                java.util.Map mapComponentSettings)
                throws Exception;
}

However, I no longer think extending the interface makes sense - the 
lifetime and address space of a configurable component will not always be 
the same as for an associated management application.
I suspect the description of the expected configuration settings will need 
to be published in a separately distributable document in some format - 
like XML Schema - that is not specific to any serialized format - like 
XML.

Thanks,
Mike

higgins-dev-bounces@xxxxxxxxxxx wrote on 05/18/2007 11:05:16 AM:

> I think maybe you misunderstand what a configurable component is - it is 

> just a component that can be configured thru the API - It is not a repo 
> for configuration data.
> I do not think a configurable component should be responsible for 
caching 
> and providing its configuration to management applications.
> I think management applications should invoke the configure method 
during 
> initialization and whenever the configuration changes.
> 
> Thanks,
> Mike
> 
> 
> higgins-dev-bounces@xxxxxxxxxxx wrote on 05/18/2007 10:18:46 AM:
> 
> > 
> > Mike, you've included separate maps for global vs. component-
> > specific settings.  I understand the motivation for this, I think, 
> > but how far do you think this separate should be continued?  For 
> > example, it seems to me that there should be a getConfiguration 
> > method for IConfigurableComponent, so that a management application 
> > (for instance) can retrieve the settings and present them to a user.
> > Should the component therefore keep the two sets of setting 
> > separate, and should there be separate getGlobalConfig and 
> > getComponentConfig methods to retrieve them?
> > 
> > ...Greg
> > 
> > 
> > 
> > Michael McIntosh wrote: 
> > I checked in several projects earlier today including:
> >         org.eclipse.higgins.configuration.api
> >         org.eclipse.higgins.configuration.common
> > 
> > Thanks,
> > Mike
> > 
> >   _______________________________________________
> > higgins-dev mailing list
> > higgins-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/higgins-dev
> 
> _______________________________________________
> higgins-dev mailing list
> higgins-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/higgins-dev