logging-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hans Kool <h...@kool.name>
Subject Re: Chainsaw V2
Date Thu, 18 Aug 2005 17:11:43 GMT
Hi Scott,

Thanks for the quick reply & good advise! Very nice to read such a good 
and extensive explanation :-)

Stupid me! I completely overlooked the download. I assumed it was a 
download for kickstarting JXTA(!) As a stupid silly foreigner I probably 
misinterpreted the line, assuming it was targeted at Javaws, instead of 
Chainsaw... *blush* *grin*

Btw, got a good reply from a german guy as well, he recommended creating 
a  hyperlink to the  .jnpl file in the cache and starting that with 
c:\windows\system32\javaws. That's how he did it (I checked it, it 
works), but I guess your advise is even much more in place.

I assume I will be looking into Chainsaw a lot for the time being, so if 
I have suggestions or can help improve it, I will definately let you know.

For now: maybe others finding out the existence of v2 would like to know 
the info described by you in this email, so maybe a small update of the 
Chainsaw page would help a lot and keep away more questions like mine. 
Up to you (or any other maintainer) of course. Hope it will release 
soon, it looks very useful and promising.

Thanks for everything and keep up the good work Scott,


Hans Kool

Scott Deboy schreef:

>1. On the Chainsaw page you linked to, right below the 'Launch' web
>start link, there is a 'download' link that provides the jars.
>2. You can specify the location of a config file that should be loaded
>whenever Chainsaw starts from the view-show application wide preferences
>window - place the URL to your config file in the 'automatic
>configuration URL' field at the bottom of the preferences window
>2. You could use the 'no receivers defined' popup that comes up when
>Chainsaw doesn't have a configuration, select 'browse for a
>configuration', select it, and then check the 'don't show me this again'
>3. As of log4j 1.3, Chainsaw is no longer included in the core jar -
>it's available as a separate download.  It's also moved to its own cvs
>repository (logging-chainsaw) - see
>3. Chainsaw v2 has a dependency on log4j 1.3 apis, so we will maintain
>compatibility with log4j 1.3 forward.  There is a plan to improve
>backward compatibility with log4j 1.2.x before the official release of
>log4j 1.3 and Chainsaw V2 (currently Chainsaw V2 can receive logging
>events from a log4j 1.2.x socketappender, but only if the events don't
>contain location info or MDC).
>3. There used to be a link to Chainsaw's page off of log4j's page, but
>it disappeared a while back.  I've made a change to fix that but I
>haven't updated the site yet.  Chainsaw hasn't disappeared.  Yes, we
>started writing Chainsaw v2 over two years ago, and yes, we still
>haven't had an officiall release.
>4. If you have any other suggestions or comments, please let us know (we
>would love the feedback).  If you feel like pitching in and helping,
>even better.
>-----Original Message-----
>From: Hans Kool [mailto:hans@kool.name] 
>Sent: Thursday, August 18, 2005 2:53 AM
>To: general@logging.apache.org
>Subject: Chainsaw V2
>Hi all,
>I caught an eye on Chainsaw v2
>(http://logging.apache.org/log4j/docs/chainsaw.html) and have three
>1. download
>Nice webstart download, but it would be good to mention how to start
>Chansaw 2 (manually) again later. Can't find where the jar is located...
>Where is it?
>2. configuration
>It would be a good thing to mention if/where to modify the log4j
>configuration to use Chainsaw, bot for log4j.properties and log4j.xml
>3. status
>Little info is given about the Chainsaw status. I noticed it is not
>(yet) in log4j. Current log4j contains the old version. When is it
>expected? What is the status?
>I hope these suggestions will be followed up soon and.. I hope to find
>out about the answers as well, because I can't wait to start using this
>fancy looking tool! :-) If anyone can answer me about these problems:
>please ;-)
>Keep up the good work,
>Hans Kool

View raw message