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=17511>.
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=17511

Patch for Chainsaw to utilise Receiver framework

           Summary: Patch for Chainsaw to utilise Receiver framework
           Product: Log4j
           Version: 1.3alpha
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Other
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


Please find attached a patch file for existing classes, plus some
attachments for additional classes for Chainsaw, and the example log4j.xml
file that can be used to start it using the Receiver model.

I've verified that after the "jar" target has been run, Chainsaw can start
on W2K using the following command(from the root of the jakarta-log4j
directory):

%JAVA_HOME%\bin\javaw.exe -cp
.;log4j-1.3alpha.jar;log4j-chainsaw-1.3alpha.jar;dist\classes
org.apache.log4j.chainsaw.Start

Notes:
======
1) Note the new Start class that does the Log4J initialization, I've
replaced the Main.main() method with a call to the Start class for legacy
support

2) Currently looks for the log4j.xml file using a Classloader.getResource()
or asks the user via JFileChooser.  I still need to add a strategy to first
check for the system property, but that is a pretty minor addition.

3) The LoggingReceiver class is now no longer used (relies on the
SocketReceiver being configured to receive events into the local log4j
environment)

4) Still only supports a single Chainsaw panel, not sure where the
multi-panel support others are working at the moment, but should be easy to
integrate.

5) I've taken the liberty of applying the Apache 1.1 licence contained in
some of the other files to all the other files, and optimizing the imports.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to