You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2003/05/12 19:57:34 UTC

DO NOT REPLY [Bug 19861] New: - Allow override of calls to System.getProperty() in applet mode

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19861>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19861

Allow override of calls to System.getProperty() in applet mode

           Summary: Allow override of calls to System.getProperty() in
                    applet mode
           Product: Log4j
           Version: 1.2
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Configurator
        AssignedTo: log4j-dev@jakarta.apache.org
        ReportedBy: glen_lewis@hotmail.com


When using log4j to log from an applet, the System properties used by 
LogManager cannot be accessed.  This disables major parts of the 
configurability of log4j.

Perhaps OptionConverter could fix this.  When running as an applet, 
OptionConverter could use its own Properties object for the log4j properties 
(private to OptionConverter).  You can detect applet mode by checking whether 
for System.getProperty( "java.home" ) craps out 
(http://java.sun.com/sfaq/index.html).

Then, I could make a couple of calls into OptionConverter before initializing 
the rest of log4j ... it would get the properties and I'd be golden ;)

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