Return-Path: Delivered-To: apmail-logging-log4j-user-archive@www.apache.org Received: (qmail 58689 invoked from network); 10 Sep 2008 05:11:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Sep 2008 05:11:34 -0000 Received: (qmail 94068 invoked by uid 500); 10 Sep 2008 05:11:29 -0000 Delivered-To: apmail-logging-log4j-user-archive@logging.apache.org Received: (qmail 94043 invoked by uid 500); 10 Sep 2008 05:11:29 -0000 Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Users List" Reply-To: "Log4J Users List" Delivered-To: mailing list log4j-user@logging.apache.org Received: (qmail 94032 invoked by uid 99); 10 Sep 2008 05:11:29 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Sep 2008 22:11:29 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Sep 2008 05:10:30 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1KdHym-000160-Uo for log4j-user@logging.apache.org; Tue, 09 Sep 2008 22:11:00 -0700 Message-ID: <19406417.post@talk.nabble.com> Date: Tue, 9 Sep 2008 22:11:00 -0700 (PDT) From: NehaG To: log4j-user@logging.apache.org Subject: Internationalization Support for JMSAppender in log4j MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: neha.gupta5@wipro.com X-Virus-Checked: Checked by ClamAV on apache.org Hello Does JMSAppender support Internationalization? As per my research, FileAppender and ConsoleAppender supports internationalization through the following configuration: log4j.appender.MyAppender.Encoding=UTF-8 Is there a similar configuration possible for JMS Appender as well? because when I am using similar configuration for JMSAppender as below: log4j.appender.JMSApp=org.apache.log4j.net.JMSAppender log4j.appender.JMSApp.Encoding=UTF-8 the output is as follows: log4j:WARN No such property [encoding] in org.apache.log4j.net.JMSAppender. log4j:ERROR Error while activating options for appender named [JMSApp]. Whereas similar configuration seems to work with File and Console Appender. If somebody have a hint, please let me know. -- View this message in context: http://www.nabble.com/Internationalization-Support-for-JMSAppender-in-log4j-tp19406417p19406417.html Sent from the Log4j - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org For additional commands, e-mail: log4j-user-help@logging.apache.org