At 13:51 21.11.2002 -0800, you wrote:
> > How do you envision this working? Can you please provide an example? > > I was thinking about something similar to ant's syntax, > > <!-- Load properties from a file --> > <property file="log4j.properties"/> > > <!-- Explicitely define a property --> > <property name="smtp.host" value="smtp.mycompany.com"/> > > Not sure if this is feasible... the DTD would need to be updated > to support this new 'property' element.
It is certainly feasible. It shouldn't be too hard to implement.
It would be interesting to have the DOMConfigurator support it's own Properties object, setting the property key/values from the property tags in the config file. The code doing the substitution could first look in the DOMConfigurator Properties object first, and if no value is found there fallback to the system properties. Interesting.
We can imitate Ant with its property task. Both <property name="foo.dist" value="dist"/> and <property file="foo.properties"/> should be possible.
-Mark
-- Ceki TCP implementations will follow a general principle of robustness: be conservative in what you do, be liberal in what you accept from others. -- Jon Postel, RFC 793 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
