Kelvin Tan wrote:
Repeat: if you use jxpath to make that implementation of the Configuration interface, you get pluggability for free. Or maybe you don't know what jxpath is.On Wed, 04 Dec 2002 14:25:10 +0100, Nicola Ken Barozzi said:hmmmm...I'm not too sure what you're getting at. I'm kinda referring to something which adheres the Configuration interface, but for XML files.In the Ant codebase, in the proposals/embed dir, ther is a task that uses jxpath for configuration. JXPath can make use of more things than just XML, and is thus much more flexible, and has xpath support. I'd take a look at that file and give that a shot for config.
Many projects use xml configuration files, and its odd that each project has its own implementation. Isn't that what the configuration sub-project is for (and Commons as a whole), to factor out common components?If you want to make sonething that is used project-wide, then look at what is already there, and factor out a common denominator.
Avalon has a Configuration, and will not switch to the Commons easily.
The minus side, of course, is tagging on another lib dependency, dom4j in this case.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
