Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <3B332DE1.40802@hartle-klug.com>
Date: Fri, 22 Jun 2001 13:37:05 +0200
From: Michael Hartle <mhartle@hartle-klug.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 0.8) Gecko/20010215
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: [C2]: Problems with content aggregation and redirects
References: <GMEBIBHGAOFGJCDPJANDKEKECDAA.cziegeler@sundn.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Carsten Ziegeler wrote:

> The CA example doesn't work as the aggregated part (moreover/moreover.xml)
> has no EventPipeline (it's a redirect).
> 
> I think we should fix this. The easiest solution for this would be to make
> the cocoon: url work and use them from inside the ContentAggregator as well.
> 
> What do you think?

Will the cocoon: protocol then later be used as the only way for to 
specifiy the source of an aggregation
element ? If it is not so, then there would be two ways how aggregations 
can be used (with or without the
cocoon: protocol) and this counter-intuitive issue regarding sitemap 
redirects that are not being resolved
would remain.

Michael


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org