Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 71202 invoked from network); 30 Dec 2004 09:40:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 30 Dec 2004 09:40:34 -0000 Received: (qmail 77058 invoked by uid 500); 30 Dec 2004 09:40:14 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 76957 invoked by uid 500); 30 Dec 2004 09:40:12 -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 76819 invoked by uid 99); 30 Dec 2004 09:40:10 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=FORGED_RCVD_HELO X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from mf01.sitadelle.com (HELO smtp.cegetel.net) (212.94.174.78) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 30 Dec 2004 01:40:06 -0800 Received: from [192.168.0.101] (80-125-210-68.dti.cegetel.net [80.125.210.68]) by smtp.cegetel.net (Postfix) with ESMTP id B4F6B3793D for ; Thu, 30 Dec 2004 10:40:03 +0100 (CET) Message-ID: <41D3CCF3.70500@apache.org> Date: Thu, 30 Dec 2004 10:40:03 +0100 From: Sylvain Wallez Organization: Anyware Technologies User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: Splitting cocoon.xconf: done References: <41D318CA.7090708@apache.org> <41D3BB62.5070706@apache.org> In-Reply-To: <41D3BB62.5070706@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Carsten Ziegeler wrote: > Great work, Sylvain! Thanks! > Just one questions below: > > Sylvain Wallez wrote: > >> Hi all, >> >> I just committed the new feature that allows cocoon.xconf to be split >> into small parts. There is a new statement that >> includes either a roles file or a xconf file. A minimal >> sourceresolver is setup at cocoon boot time that provides the >> "resource:" and "context:" protocols to fetch files (relative files >> are equivalent to "context:"). > > > Why are relative files resolved relative to the context and not to the > location of the cocoon.xconf? Good question :-) At first, I thought relative URIs should be relative to the current file, but then looked at how sourceresolving is done everywhere else in Cocoon: URIs are relative to the current sitemap (i.e. the context in case of the root sitemap): "src" attributes in the sitemap, includes in CInclude and XInclude, etc. AFAIK, only XSLT's includes and imports are handled differently because it's mandated by the XSLT spec. So, I decided to use the standard sourceresolving mechanism in xconf also. How does that sound? Sylvain -- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }