Jini 2.0 was just released. It supports a new type of configuration files
that is very interesting (at least to me). In fact there is a
ConfigurationProvider that exposes Configuration implementations. By now the
only Configuration implementation is the ConfigurationFile.

The ConfigurationFile supports a subset of Java code! So a use could be:

  Configuration config =
            ConfigurationProvider.getInstance("my_config_file.config");

  ExpectedClass instance = (ExpectedClass) config.getEntry(
            "mynamespace.myclass.mysettingkey",
            "objectname",
            ExpectedClass.class);

And the my_config_file.config file:

import mynamespace.*;

mynamespace.myclass.mysettingkey
{
    objectname = new ExpectedClass("someconfig");
}

mynamespace.myclass.mysettingkey2
{
    map = new HashMap();
    map.add( "key", "value");
}


I think it's a evolution and should be considered as a different
configuration strategy that avalon could support.
More on that can be found at
http://pandonia.canberra.edu.au/java/jini/tutorial/Config.xml


Thoughs?

hammett


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

Reply via email to