Hi all,
Is there currently any activity/planning/effort going on in Commons
Configuration. I'm interested in an adaptation of the framework which
could be contributed back into the project if found acceptable.
Specifically in the following areas:
1.) wildcards, regexp is File Selections for properties and xml
properties files
<properties fileName="conf.d/*.properties"/>
2.) A factory loading strategy that unifies the loading of properties
irrespective of the file format (similar to the "include" property)
but more like JSP/XSL include/import semantics. This means that
override and additional directives would be parameterized into the
includes such that the factory only needs to know where the root
config file is located and the factory config.xml becomes obsolete.
Instead, its syntax becomes a separate data model from the xml format
and reusable throughout configuration properties files irrespective
of file format.
Finally.
3.) Configuration is really doing something that would be best
captured in a JNDI Context such that there was no need to know about
Apache Configuration to actually access the properties, thus
something like a Commons Configuration JNDI Service provider would allow
javax.naming.Context ctx = new InitialContext("java:comp/env/config/
MyConfig"...);
String fooBar = (String) ctx.lookup("foo.bar");
With configuration in the web.xml as follows:
<resource-ref>
<description>Resource reference to a Jakarta Commons
Configuration.</description>
<res-ref-name>config/MyConfig</res-ref-name>
<res-type>org.apache.commons.configuration.ConfigurationContext</
res-type>
</resource-ref>
This would allow one to load a Configuration source as a JNDI
resource in a webapplication web.xml or in tomcats server.xml and
keep the source of that configuration very separate from its usage in
the web-app.
Cheers.
-Mark
Mark R. Diggory
~~~~~~~~~~~~~
DSpace Systems Manager
MIT Libraries, Systems and Technology Services
Massachusetts Institute of Technology
-- and an Apache Jakarta Commons Commiter...
