Thanks a lot it is working fine. Regards, Deepesh
-----Original Message----- From: Ceki Gülcü [mailto:ceki@;qos.ch] Sent: Monday, November 11, 2002 6:41 PM To: Log4J Developers List Subject: Re: Help Required on Log4J Deepesh, In the Category class there is a method called log which is designed to support wrappers. Its signature is: log(String callerFQCN, Priority level, Object message, Throwable t) where callerFQCN is the fully qualified name of the calling class. The next version of the complete manual explains this in some detail. However, it is not yet available. I hope this helps. At 18:04 11.11.2002 +0530, Deepesh Jain wrote: >Hi, >I am using log4J for logging in my application. >I have made the wrapper class for logging which in turn calls log4J API's >but when I use wrapper class in my application and log the message in the >file, logged messages contain the wrapper class name and wrapper class >function name which calls the Log4J API instead of application class name >and application method name . > >Can you please suggest some way out to solve the problem. >Quick response is highly appreciated. >Thanks in advance. > >Regards, > >Deepesh -- Ceki TCP implementations will follow a general principle of robustness: be conservative in what you do, be liberal in what you accept from others. -- Jon Postel, RFC 793 -- To unsubscribe, e-mail: <mailto:log4j-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:log4j-dev-help@;jakarta.apache.org> ____________________________________________________ INTIQUA International Intelligent Solutions, Quality Execution ____________________________________________________ Note: The information and data contained in this message (and attachments) may be privileged and confidential and protected from disclosure to any party or parties apart from the intended recipient. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer.
