Since these appserver attributes don't change during the course of
execution, I think that would work fine so long as the app server only used
SocketAppenders. But I think it is common to use console and file
appenders to log things locally in addition to logging to a socket. There
would still have to be some way to get the appserver attributes into the
logging event.
- Paul
Paul Glezen
IT Specialist
Software Services for WebSphere
818 539 3321
Ceki G�lc� <[EMAIL PROTECTED]> on 09/03/2001 03:12:54 PM
Please respond to "LOG4J Developers Mailing List"
<[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: AppServer example
Hi Paul,
Have you considered extending SocketAppender to send parameters such as
server name, version, components attribute etc. when connecting to
the SocketServer? In such case, there would be no need to extend the
Category class.
Another solution is to use MDCs to set parameters. They will be
automatically
sent to the server and printed there. Regards, Ceki
--
Ceki G�lc� - http://qos.ch
---------------------------------------------------------------------
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]
