Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 90492 invoked from network); 25 Sep 2006 13:02:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 25 Sep 2006 13:02:11 -0000 Received: (qmail 29852 invoked by uid 500); 25 Sep 2006 13:01:56 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 29807 invoked by uid 500); 25 Sep 2006 13:01:56 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 29777 invoked by uid 99); 25 Sep 2006 13:01:56 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Sep 2006 06:01:56 -0700 Authentication-Results: idunn.apache.osuosl.org header.from=ddevienne@gmail.com; domainkeys=good Authentication-Results: idunn.apache.osuosl.org smtp.mail=ddevienne@gmail.com; spf=pass X-ASF-Spam-Status: No, hits=0.5 required=5.0 tests=DNS_FROM_RFC_ABUSE Received-SPF: pass (idunn.apache.osuosl.org: domain gmail.com designates 64.233.182.184 as permitted sender) DomainKey-Status: good X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 Received: from [64.233.182.184] ([64.233.182.184:50629] helo=nf-out-0910.google.com) by idunn.apache.osuosl.org (ecelerity 2.1.1.8 r(12930)) with ESMTP id 32/D6-13750-043D7154 for ; Mon, 25 Sep 2006 06:01:52 -0700 Received: by nf-out-0910.google.com with SMTP id x29so1443987nfb for ; Mon, 25 Sep 2006 06:01:47 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=OUVwVzSXvnQkn+aeUtzDfW9Rksh36cdPJZaSI0W14rqWpNuY2dXAYD96kMJAkMEg4wc2yzeKvG/hr2POiMjf012i25fSCJ4hu5HHrBDXgbrBwDOKCCEy8husKOIoi+ZAG2ASMHw70gdPSLYTBFFx+L8OD0PLv4IB7cTlbu0OlBY= Received: by 10.49.94.20 with SMTP id w20mr1403818nfl; Mon, 25 Sep 2006 06:01:47 -0700 (PDT) Received: by 10.49.64.15 with HTTP; Mon, 25 Sep 2006 06:01:47 -0700 (PDT) Message-ID: <255d8d690609250601q3392e955v35c8078285f0c219@mail.gmail.com> Date: Mon, 25 Sep 2006 08:01:47 -0500 From: "Dominique Devienne" To: "Ant Developers List" Subject: Re: Resource.getURL() In-Reply-To: <4517ADDF.1020002@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <255d8d690609230856q119631dbx17081ad38cb366ce@mail.gmail.com> <006601c6df93$66c486e0$0301a8c0@julia> <255d8d690609241757o4c57e60s3316549dce799be7@mail.gmail.com> <4517ADDF.1020002@gmx.de> X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N > > The question is why would you need to get back a URL from a Resource? > You need to get a URL from a resource if you want to use the resource as > InputSource in XML processing. > The URL is used to set the SystemId, in practice to be able to resolve > includes, entities, ... which are to be found with a relative path. But when you get a StringResource, or PropertyResource, which are ficticious Resource impls wrapping a string or the value of an Ant property, even if you wrap these into a custom URL, how would you resolve URLs relative to these??? This is the reason why I'm saying that a getURL only makes sense for true URLResources only. Pushing it down to Resource smells wrong to me. Even if I'm wrong, it's easier to push it down to Resource afterward, based on community experience, rather that putting it there in the first place IMHO. --DD --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org