Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 3851 invoked from network); 20 Oct 2004 17:48:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 20 Oct 2004 17:48:19 -0000 Received: (qmail 70145 invoked by uid 500); 20 Oct 2004 17:48:16 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 70056 invoked by uid 500); 20 Oct 2004 17:48:15 -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 70042 invoked by uid 99); 20 Oct 2004 17:48:15 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [192.18.33.10] (HELO exchange.sun.com) (192.18.33.10) by apache.org (qpsmtpd/0.28) with SMTP; Wed, 20 Oct 2004 10:48:15 -0700 Received: (qmail 3210 invoked by uid 50); 20 Oct 2004 17:50:17 -0000 Date: 20 Oct 2004 17:50:17 -0000 Message-ID: <20041020175017.3209.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: commons-dev@jakarta.apache.org Cc: Subject: DO NOT REPLY [Bug 31807] New: - [chain] sample catalog.xml missing tag X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31807 [chain] sample catalog.xml missing tag Summary: [chain] sample catalog.xml missing tag Product: Commons Version: Nightly Builds Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: chain AssignedTo: commons-dev@jakarta.apache.org ReportedBy: sean.schofield@gmail.com Newest code is working great, except I ran into a small problem. Digester wasn't parsing the catalog.xml I was providing through chain-listener. I discovered that by adding a tag as the root of my xml (which used to be ) then everything worked fine. I believe the problem was that because I did not specify a 'org.apache.commons.chain.CONFIG_ATTR' it called the overloaded parseWebResources method of ChainResources that omits the catalog argument. It appears that this method was intended for when you already have a catalog on the stack and want to add to it, but I'm not sure on that. In any event, without the tag, Digester complained that the stack was empty. I don't think there is a really a bug here, but the catalog.xml included in the examples should probably show a tag since this is what many people will be using as a reference when creating there own. I will supply a patch when I get home tonight. --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org