Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 2241 invoked from network); 5 Mar 2004 06:21:22 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 5 Mar 2004 06:21:22 -0000 Received: (qmail 95790 invoked by uid 500); 5 Mar 2004 06:20:59 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 95395 invoked by uid 500); 5 Mar 2004 06:20:57 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 95381 invoked from network); 5 Mar 2004 06:20:56 -0000 Received: from unknown (HELO confixx.bestiole.ch) (66.111.0.243) by daedalus.apache.org with SMTP; 5 Mar 2004 06:20:56 -0000 Received: from apache.org (lsn-boi-catv-c121-p001.vtx.ch [212.147.121.1]) by confixx.bestiole.ch (8.11.6/8.11.6) with ESMTP id i256L6P03353 for ; Fri, 5 Mar 2004 07:21:06 +0100 Date: Fri, 5 Mar 2004 07:21:04 +0100 Subject: Re: DO NOT REPLY [Bug 27432] New: - Malformed HTTP headers (debug information in Parameters object) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Mime-Version: 1.0 (Apple Message framework v553) From: Bertrand Delacretaz To: dev@cocoon.apache.org Content-Transfer-Encoding: quoted-printable In-Reply-To: <4047A623.1060909@apache.org> Message-Id: <47B111B0-6E6D-11D8-9EDE-000393CFE402@apache.org> X-Mailer: Apple Mail (2.553) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Le Jeudi, 4 mars 2004, =E0 22:56 Europe/Zurich, Sylvain Wallez a =E9crit = : > ....Although individual parameter location may be useful, the location=20= > parameter I'm talking about is that of the statement. This makes me=20 > think "SitemapParameters" with a "getStatementLocation()" is better=20 > than "LocatedParameters" I suggested above. > > Let's consider the following snippet: > 10 ... > 11 > 12 > 13 > 14 ... > > ((SitemapParameters)parameters).getStatementLocation() -->=20 > "sitemap.xmap:11:2" > parameters.getLocation("bar") --> "sitemap.xmap:12:4" > > getLocation(name) can be useful to notify a problem about a particular=20= > parameter, while getStatementLocation() relates to the whole > = statement. > > getLocation(name) can also be useful for Parameterizable components,=20= > as it replaces Configuration.getLocation() which is no more available. Sounds good, having both is certainly useful for error reporting. Just a detail, how about casting to a SitemapLocation interface instead=20= of classes? ((SitemapLocation)parameters).getStatementLocation() -->=20 "sitemap.xmap:11:2" And assuming you get plain Parameters ((SitemapLocation)parameters).getParameterLocation("bar") ->=20 "sitemap.xmap:12:4" -Bertrand