Re: [Figleaf-developer] Application configuration

[Greg S. <ste...@on...>]

sam...@ma... wrote:

>As I see it, at this stage of the game we need to configure the following things:
>
>1. Which persistence mechanism to use
>2. Which UI mechanism to use
>3. Which Object manager to use
>4. Which classes to use
>
>How about an ApplicationConfiguration interface which defines the folowing methods:
>
>getPersistenceMechanism()
>getUIMechanism()
>getObjectManager()
>getRegisteredClasses()
>
>The default ApplicationConfiguration implementation will use Spring - it will be
>up to the bootstrapper class (or whatever) to invoke the correct configuration.
>Even if we do use Spring, it would be nice to keep any configuration files as
>simple as possible - the AppicationContext files can get a little verbose, so we
>may want to roll our own configuration file. I can code up an implementation
>that uses Spring's configuration file behind the scenes if you want - it will
>just act as an abstracted layer for the code you already have. I'll probably
>also code an implementation which allows the user to code the configuration
>directly.
>
>sam
>http://www.magpiebrain.com/
>
>
>  
>
I think a configuraion API is a good idea - it would be convenient to be 
able to configure in ways other than an XML file (like getting it from a 
database or programmatically). However, I wouldn't consider it a 
critical feature at this time. Our interfaces are likely to change 
rapidly at the beginning, and therefore the configuration interface will 
have to keep changing also. That makes just changing an XML file a good 
approach for now, particularly since I can just add any property to the 
xml file and Spring automatically sets it with the correct 
values/references.

What about the Introspector work?

Greg