Return-Path: Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 39271 invoked by uid 500); 29 Jul 2003 15:17:21 -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 39167 invoked from network); 29 Jul 2003 15:17:20 -0000 Received: from unknown (HELO host.leverageweb.com) (64.91.232.157) by daedalus.apache.org with SMTP; 29 Jul 2003 15:17:20 -0000 Received: from dhcp205061.hq.af.mil ([134.205.205.61] helo=leverageweb.com) by host.leverageweb.com with asmtp (Exim 3.36 #1) id 19hWBI-0004oA-00 for dev@cocoon.apache.org; Tue, 29 Jul 2003 11:14:28 -0400 Message-ID: <3F268FFD.8090504@leverageweb.com> Date: Tue, 29 Jul 2003 11:17:17 -0400 From: Geoff Howard User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3.1) Gecko/20030425 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: Treeprocessor bug with map:resource and views? References: <3F267E82.7030404@verizon.net> In-Reply-To: <3F267E82.7030404@verizon.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host.leverageweb.com X-AntiAbuse: Original Domain - cocoon.apache.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0] X-AntiAbuse: Sender Address Domain - leverageweb.com X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Vadim Gritsenko wrote: > Hi guys, > > Check out the samples. Most of them work ok, with the exception of i18n > samles -- click on content view or links view and see the results. i18n > samples use aggregation and resources in the sitemap with the label on > one aggregated part. When this pipeline moved from the resource to the > pipelines section everything seems to be working ok. > > This makes me think that there is a problem with resource handling and > view labels in the tree processor. Anybody seen this issue already? I don't have a running copy available ATM - can you describe the results you're seeing? I've noticed a problem with those links that I think is more due to the sitemap/xsl design that handles them and am wondering if we're seeing the same thing. Geoff