Return-Path: 
 <dev-return-69661-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@www.apache.org
Received: (qmail 33567 invoked from network); 21 Dec 2004 07:48:09 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 21 Dec 2004 07:48:09 -0000
Received: (qmail 57980 invoked by uid 500); 21 Dec 2004 07:47:52 -0000
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 57875 invoked by uid 500); 21 Dec 2004 07:47:50 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
list-post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 57835 invoked by uid 99); 21 Dec 2004 07:47:49 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Received: from postfix4-1.free.fr (HELO postfix4-1.free.fr) (213.228.0.62)
  by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 20 Dec 2004 23:47:46 -0800
Received: from [192.168.0.100] (lns-vlq-39f-81-56-134-235.adsl.proxad.net
 [81.56.134.235])
	by postfix4-1.free.fr (Postfix) with ESMTP id BD5DD22FDEB
	for <dev@cocoon.apache.org>; Tue, 21 Dec 2004 08:47:43 +0100 (CET)
Message-ID: <41C7D51E.3040304@apache.org>
Date: Tue, 21 Dec 2004 08:47:42 +0100
From: Sylvain Wallez <sylvain@apache.org>
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 (was Re: Cocoon, a Huge, Scary Beast?)
References: <329A68716B57D54E8D39FD3F8A4A84DF350EDE@um-mail0136.unimaas.nl>
 <0DE49E8C-5014-11D9-A995-000A958B684A@outerthought.org>
 <41C3063F.1080106@nada.kth.se> <41C5E575.6050107@apache.org>
 <41C5EA4E.6010008@umn.edu> <41C5ECDF.5090003@apache.org>
 <41C6976E.2080407@outerthought.org> <41C6B61C.7070207@apache.org>
 <41C6CB56.3090703@apache.org>
In-Reply-To: <41C6CB56.3090703@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

Reinhard Poetz wrote:

> Sylvain Wallez wrote:
>
>> The result is that to activate/deactivate a block, you'll simply have 
>> to decomment/comment a line in the main cocoon.xconf. Example:
>> <cocoon>
>>  <!-- block-specific components -->
>>  <import src="cocoon-pdf-block.xconf"/>
>>  <import src="cocoon-portal-block.xconf"/>
>>  <import src="cocoon-svg-block.xconf"/>
>>
>>  <!-- the core cocoon components (parser, cache, pipelines, etc) -->
>>  <import src="cocoon-core.xconf"/>
>> </cocoon>
>
>
> two thoughts:
> 1. once on icq we chatted about implicit .xconf files to enable 
> blocks. this goes into the same direction, doesn't it? Imean if i 
> deploay a block inzo WEB-INF/blocks, it isn't necessary to make an 
> explicit import.


Well, WEB-INF/blocks isn't there yet, but yes, there could be some 
implicit imports from deployed blocks. I finally chose an explicit 
<import> statement for the main cocoon.xconf rather than loading 
WEB-INF/*.xconf in order for this feature to work in the less magical 
and therefore the more predictible and understandable way.

> 2. how does this relate to carsten's proposal, that we are voting on?


<import> will come for free in <map:components> also. We may want to 
keep a uniform syntax between xconf and xmap or have a different one 
with <map:components src="blah.xconf"/>, which actually easily 
translates to an xconf with a single <import>. I have no particular 
preference for one syntax or the other ATM...

Sylvain

-- 
Sylvain Wallez                                  Anyware Technologies
http://www.apache.org/~sylvain           http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }