After looking through the Javadocs, if I wanted to provide a Configuration backed by commons-configuration, then I should implement the org.apache.framework.configuration.Configuration interface. I guess it should pass the DefaultConfigurationTestCase as well. I can look at the NamingConfigurationBuilder in the avalon-excalibur CVS repo for a pattern to follow..
But I think what I am not understanding is how to tell excalibur that I have a different ConfigurationBuilder to use... Should I be looking at the avalon-excalibur repo at all? Or should I focus on trying to figure out fortress? Eric > -----Original Message----- > From: Berin Loritsch [mailto:[EMAIL PROTECTED] > Sent: Monday, September 08, 2003 3:14 PM > To: Avalon framework users > Subject: Re: Changing the ConfigurationBuilder > > > Eric Pugh wrote: > > > Has there been anythought in how to provide configuration > values from a > > different source? In Turbine, we use > Commons-configuration, which is nice > > because you can pull config values from XML, .properties, > JNDI, etc.. I > > would like to be able to have the avalon configuration > class interface/pull > > from a commons-configuration Configuration class. Any > pointers to get me > > started? > > In the Excalibur Configuration package, we have a > ConfigurationBuilder that > reads from LDAP. Anything is possible. It's just that the > XML files have > suited so many people's needs just fine that few folks have > proposed or offered > anything else. > > > -- > > "They that give up essential liberty to obtain a little > temporary safety > deserve neither liberty nor safety." > - Benjamin Franklin > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
