Re: Chainsaw Tab identifier

2008-03-06 Thread Jason Tholstrup
bit is no big deal. Once I've got this all flushed out and working would you like me to send you the upgraded version of SocketHubAppender? Any guide lines I'd need to follow to contribute it back? Jason Tholstrup Software Engineer [EMAIL PROTECTED] On Mar 6, 2008, at 11:12 A

Re: Chainsaw Tab identifier

2008-03-05 Thread Jason Tholstrup
tApplication(String lapp) { this.application = lapp; } /** * Returns value of the Application option. */ public String getApplication() { return application; } Jason Tholstrup Software Engineer [EMAIL PROTECTED] O

Re: Chainsaw Tab identifier

2008-03-03 Thread Jason Tholstrup
and be able to configure our appenders as you describe (we have access to the log4j.properties file on the server)? Thanks for being patient and walking me through all of this. You've easily save me a couple of days of bumbling around trying to get this to work. Jason Tholstrup Software E

Re: Chainsaw Tab identifier

2008-03-03 Thread Jason Tholstrup
rg/log4j/"; debug="true"> class="org.apache.log4j.net.SocketHubReceiver"> Jason Tholstrup On Mar 3, 2008, at 11:42 AM, Scott Deboy wrote: Two things: 1. To get every socketappender connection to display in its own tab in Chai

Re: Chainsaw Tab identifier

2008-03-03 Thread Jason Tholstrup
looking at the right javadocs that's enough. I'd just like to be able to tinker on my own. Thanks for all your hard work. Chainsaw is pretty cool. Jason Tholstrup Software Engineer [EMAIL PROTECTED] On Mar 3, 2008, at 11:42 AM, Scott Deboy wrote: Two things: 1. To get every socketapp

Chainsaw Tab identifier

2008-03-03 Thread Jason Tholstrup
ThrowableInformation * TIMESTAMP timestamp Long * THREAD threadString * PROP.keyName entry in the Property hashtable String * mapped to the key