Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Message-ID: <3F78518D.7030208@apache.org>
Date: Mon, 29 Sep 2003 11:36:45 -0400
From: Ted Husted <husted@apache.org>
Organization: Apache Software Foundation - Jakarta Project
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
MIME-Version: 1.0
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: [Chain] ChainServlet first draft
References: <029401c38607$8647c790$edd4fea9@radpbi.bah.com>
 <040e01c38611$82124fb0$edd4fea9@radpbi.bah.com>
In-Reply-To: <040e01c38611$82124fb0$edd4fea9@radpbi.bah.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Sgarlata Matt wrote:
 >>Attached is a first cut at creating a ChainServlet.  Committers,
 > please feel
 >>free to add this to CVS (you'll need to add the license, version #s,
 >>and change the package declaration), to modify it, or to tell me what
 >>to do to modify it (and I will do so).

Can we change it to look for the catalog as a resource on the classpath, 
instead of under the file root? Since the Catalog is a business layer 
component, it may often be maintained as part of the business classes, 
and may even be distributed in a JAR. [At least mine is :)]

Other than that, I've it up and running now in my application now.

I put it in a package under web/servlet/config. Does that sound reasonable?

I also added a static to the Catalog interface to provide a convenient 
standard for the Catalog attribute name. This will help keep various 
concrete implementations on the same page.

-Ted.