Chainsaw V2 has too many dependencies on new (1.3) features to be incorporated 
into a 1.2.x release without major rework (relies on new LoggingEvent 
constructors, receivers, etc.).  It's also available via WebStart, so there is 
no real value in working to include it in a 1.2.x release.

Chainsaw can process events from any logging framework that can write a file to 
disk in a fixed format (using LogFilePatternReceiver), can read events out of a 
database, etc.  The only log4j 1.2.x-specific capability is related to 
Chainsaw's ability to deserialize LoggingEvents generated by older versions of 
SocketAppender.

Chainsaw should be able to process files saved using 1.2.x XMLLayout - Chainsaw 
expects 'logger' and not 'category' for the name of the logger node, but this 
changed in Oct 2002.  Versions of log4j prior to Oct 2002, which used XMLLayout 
to create files, would not be able to be processed.

Properties were the only feature added to the XML with log4j 1.3 (if I remember 
correctly), and they are optional.

Scott 


-----Original Message-----
From:   Scott Heaberlin [mailto:[EMAIL PROTECTED]
Sent:   Tue 5/3/2005 8:49 PM
To:     Log4J Developers List
Cc:     
Subject:        Re: Reconsideration of features for 1.3 (Re: slf4j and log4j)
I would think that Chainsaw (as mentioned by Endre as an example in
the other thread)  would need to be withheld until at least 1.3 if not
an alluded-to 2.0 major release.  IIRC, chainsaw v2 utilizes the new
plugin / receiver framework and as a user I'd be a little hesitant to
switch to a 1.2.9+ knowing it incorporated major changes like this
while at present it is only being tested "out there" by projects
utilizing 1.3alpha.  On a related note, I believe the structure of the
XMLLayout in 1.2.x is incompatible with the xml format needed by
chainsaw v2 (at least that is what i ran into with early builds of
v2). If this is still true, then including chainsaw v2 with a 1.2.x
release will only lead to confusion.

Just my $.02,

-Scott Heaberlin

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







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

Reply via email to