Endre,
Here are a few hints that you might find useful.
1) Create a java.util.properties instance using a PropertiesAction (or some other name) similar to the <property> task in Ant.
2) Place this java.util.properties instance in the joran execution context's objectMap under a key, say "props".
3) All other Actions can access that properties instance and perform variable substitution.
That's it...
Note that you do not need to modify the classes under org.apache.joran at all. Only org.apache.log4j.joran need to be modified.
At 03:48 PM 4/27/2004, Ceki G�lc� wrote:
Endre,
DOMConfigurator will be replaced by JoranConfigurator. Adding props to JoranConfigurator should not be hard.
See http://www.qos.ch/logging/joran.pdf
there are bunch of examples/tutorial under
http://cvs.apache.org/viewcvs.cgi/logging-log4j/examples/src/joran/
I'll gladly add a PropertiesRule if you have the time to contribute it.
Don't hesitate to contact me if you need help.
At 03:36 PM 4/27/2004, Endre St�lsvik wrote:The field "props" in DOMConfigurator would be -marvelous- to be able to set. But there aren't any accessors, thus (it seems like) the only option is to extend this class and then set it (the field is protected!). It really seems like it has been the intention to be able to set this, but then no-one has gotten around to make a setter.
Suggesting to make this setter.
-- Mvh, Endre St�lsvik M[+47 93054050] F[+47 51625182] Developer @ CoreTrek AS - http://www.coretrek.com/ CoreTrek corporate portal / EIP - http://www.corelets.com/
-- Ceki G�lc�
For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
