Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 95157 invoked from network); 19 Oct 2005 11:00:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 19 Oct 2005 11:00:20 -0000 Received: (qmail 68404 invoked by uid 500); 19 Oct 2005 11:00:17 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 68346 invoked by uid 500); 19 Oct 2005 11:00:16 -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 List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 68335 invoked by uid 99); 19 Oct 2005 11:00:16 -0000 X-ASF-Spam-Status: No, hits=-10.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [209.237.227.194] (HELO [127.0.0.1]) (209.237.227.194) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Oct 2005 04:00:16 -0700 Message-ID: <435627E6.6040705@apache.org> Date: Wed, 19 Oct 2005 13:03:02 +0200 From: Carsten Ziegeler User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: Portal Block: Include coplet instance id in window renderer References: <20051019095421.GB6229@vision.anyware> In-Reply-To: <20051019095421.GB6229@vision.anyware> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Jean-Baptiste Quenot wrote: > Hello, > > There was a recent change in WindowAspect that is causing > problems: all coplet ids are now displayed in the generated > portal. > > Filtering out that extra XML element would require > us to change 56 stylesheets in a dozen projects... that's a bit > annoying. Is there any workaround besides copying the previous > class in WEB-INF/classes? > > Any input will be appreciated. Hmm, so you're stylesheets are not prepared for any additional information that might come out of the renderer? I think in general you should prepare your stylesheets for this. Anyways, we could make this configurable, but in the future the instance-id is required for new features of the portal to work, so my suggestion would be to use your own renderer for now and update your stylesheets on the long term. However, if you insist, i'll make it configurable in 2.1.8. Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/