logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 43619] - Simple proposal for pluggable sys-props resolvers
Date Fri, 26 Oct 2007 17:46:35 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=43619>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43619





------- Additional Comments From carnold@apache.org  2007-10-26 10:46 -------
Redirecting the calls that currently go to java.lang.System.getProperty(String) to another
arbitrary 
class's static getProperty(String) method, should still allow you to use JNDI in preference
to system 
properties or vice-versa.

What I meant as hard to explain is that in either case you can't say something like the default
value of 
this new property is some existing class that the user will be familiar.  

In redirecting the getSystemProperty() call, you can explain that you are redirecting the
source of all 
system properties with the exception of "log4j.systemPropertySource" and the user has some
familiarity 
with System.getProperty(String).  

In redirecting OptionConverter.substVars(), you have to say that you are redirecting from
some 
description of the current strategy or a some new class that encapsulate that strategy.

Overriding OptionConverter.getSystemProperty() would allow you, for example, to set the location
of 
the configuration file as an environment variable (assuming a JNDI implementation of getProperty())
that 
overriding OptionConverter.substVars() wouldn't.  Like:

export log4j.configuration=~/mylogconfig.xml




-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message