Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 3755 invoked from network); 2 Mar 2005 03:47:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 2 Mar 2005 03:47:47 -0000 Received: (qmail 26680 invoked by uid 500); 2 Mar 2005 03:47:46 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 26282 invoked by uid 500); 2 Mar 2005 03:47:44 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 26265 invoked by uid 99); 2 Mar 2005 03:47:44 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from rwcrmhc14.comcast.net (HELO rwcrmhc11.comcast.net) (216.148.227.89) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 01 Mar 2005 19:47:42 -0800 Received: from [192.168.2.102] (c-67-162-109-157.client.comcast.net[67.162.109.157]) by comcast.net (rwcrmhc14) with ESMTP id <20050302034740014002vkmte>; Wed, 2 Mar 2005 03:47:40 +0000 Mime-Version: 1.0 Message-Id: In-Reply-To: <37d34e6b05030113175feae402@mail.gmail.com> References: <37d34e6b05030113175feae402@mail.gmail.com> Date: Tue, 1 Mar 2005 21:46:11 -0600 To: Howard Lin , Jakarta Commons Developers List From: Joe Germuska Subject: Re: [chain] questions about various servlet/*Mapper classes Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N At 4:17 PM -0500 3/1/05, Howard Lin wrote: >I'm trying to use ChainProcessor and various servlet/*Mapper classes >(like PathInfoMapper, ServletPathMapper etc.) (version 1.0) and it >seems the following always return null catalog: > >Catalog catalog = (Catalog) context.get(getCatalogKey()); It looks like the ChainServlet hasn't caught up with the preferred mechanism for managing catalogs. Since slightly before the 1.0 release, the CatalogFactory class was introduced, which manages an arbitrary number of named catalogs (as well as one "default" catalog.) In your XML, the catalog takes a "name" attribute, and then is retrieved using CatalogFactory.getInstance().getCatalog("name") This should be filed as a bug in Bugzilla; I suspect the changes are relatively simple, but since I don't ever use the ChainServlet, I'm afraid it would take me quite a while to put together a decent test environment. It would be great if someone using it could come up with some patches! Joe -- Joe Germuska Joe@Germuska.com http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org