Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 80682 invoked from network); 21 Apr 2009 19:26:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 21 Apr 2009 19:26:07 -0000 Received: (qmail 58646 invoked by uid 500); 21 Apr 2009 19:26:06 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 58534 invoked by uid 500); 21 Apr 2009 19:26:06 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 58524 invoked by uid 99); 21 Apr 2009 19:26:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Apr 2009 19:26:06 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ralph.goers@dslextreme.com designates 209.85.146.179 as permitted sender) Received: from [209.85.146.179] (HELO wa-out-1112.google.com) (209.85.146.179) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Apr 2009 19:25:57 +0000 Received: by wa-out-1112.google.com with SMTP id j32so1676460waf.10 for ; Tue, 21 Apr 2009 12:25:35 -0700 (PDT) Received: by 10.115.14.1 with SMTP id r1mr4131163wai.171.1240341935895; Tue, 21 Apr 2009 12:25:35 -0700 (PDT) Received: from ?192.168.10.129? (adsl-66-51-196-164.dslextreme.com [66.51.196.164]) by mx.google.com with ESMTPS id j39sm9536195waf.28.2009.04.21.12.25.34 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 21 Apr 2009 12:25:35 -0700 (PDT) Message-Id: <59305DEC-5809-4BEA-85CE-942CFE6FE65D@dslextreme.com> From: Ralph Goers To: "Commons Developers List" In-Reply-To: <49EE1794.9080201@apache.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Subject: Re: commons-logging unsuited for cross-context webapplication invocation usage - migrating to slf4j? Date: Tue, 21 Apr 2009 12:25:32 -0700 References: <49ECDF6E.70502@doit.wisc.edu> <4A30EC8B-ABA6-4DC0-A766-6EB31A33B24A@dslextreme.com> <342A575A-ECF8-4892-A8B8-312B92DBCD8B@dslextreme.com> <25aac9fc0904210801g5cfcb13ao65df7df0a334fb17@mail.gmail.com> <49EE1794.9080201@apache.org> X-Mailer: Apple Mail (2.930.3) X-Virus-Checked: Checked by ClamAV on apache.org On Apr 21, 2009, at 11:59 AM, Dennis Lundberg wrote: >> > > I'm not that experienced in writing portlets or how the portlet > container works. Can you please try to explain in more detail what the > problem is. > > Commons Logging works great in a servlet container like Tomcat. Every > webapp can have their own version of commons-logging and their own > configuration. How does the portlet container use case differ from > this? > > Do you configure Commons Logging explicitly, by using a > commons-logging.properties file or are you relying on auto > discovery? In > my experience you you should *always* configure the logging > implementation explicitly if you want deterministic results. > As I said in an earlier post, I follow the various portlet mailing lists but really have very little to do with the issue they are experiencing. It is documented at http://issues.apache.org/jira/browse/PLUTO-553 . In a nutshell though, the Portal is a War. Individual portlets are packaged as separate war files and are run under the direction of the main portal war. They seem to want all the portlets to use the logging configuration of the portal. Personally, I'm not sure what they are saying they want makes sense, but I guess the point is that even if it doesn't they should still be able to do it. Ralph --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org