Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Date: Sun, 14 Apr 2002 07:02:51 +0200 (CEST)
From: giacomo <giacomo@apache.org>
To: <cocoon-dev@xml.apache.org>
Subject: Re: TreeProcessor incompatibility with compiled engine
In-Reply-To: <01db01c1e35d$eb6d3130$9274558b@vgritsenkopc>
Message-ID: <Pine.LNX.4.33.0204140700140.20455-100000@lapgp.otego.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Sat, 13 Apr 2002, Vadim Gritsenko wrote:

> Hello,
>
> Found this when tried tree processor on my sitemap:
>
> org.apache.avalon.framework.configuration.ConfigurationException: There
> must be at least one part in map:aggregate at
> file:/C:/.../sitemap.xmap:125:48
> 	at
> org.apache.cocoon.components.treeprocessor.sitemap.AggregateNodeBuilder.
> buildNode(AggregateNodeBuilder.java:158)
> 	at
> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNodeB
> uilder.buildChildNodesList(AbstractParentProcessingNodeBuilder.java:156)
>
> 	at
> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNodeB
> uilder.buildChildNodes(AbstractParentProcessingNodeBuilder.java:172)
>
>
> When using construct like:
>
>         <map:match pattern="part/categories/">
>           <map:aggregate element="categories"/>
>           <map:serialize type="xml"/>
>         </map:match>
>
> This works fine in compiled sitemap engine. Is there anybody against
> fixing this incompatibility? Possible solution could be log a warning
> instead of failing hard - if majority considers this functionality is
> not desirable.

Actually I don't know why this works with the compiled sitemap. My
understanding is that it shouldn't. I would vote to correct the
sitemap.xsl to fail hard as the TreeProcessor.

Giacomo


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