Return-Path: Delivered-To: apmail-myfaces-users-archive@www.apache.org Received: (qmail 79003 invoked from network); 8 Oct 2007 19:09:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Oct 2007 19:09:34 -0000 Received: (qmail 84244 invoked by uid 500); 8 Oct 2007 19:09:18 -0000 Delivered-To: apmail-myfaces-users-archive@myfaces.apache.org Received: (qmail 84101 invoked by uid 500); 8 Oct 2007 19:09:17 -0000 Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "MyFaces Discussion" Delivered-To: mailing list users@myfaces.apache.org Received: (qmail 84090 invoked by uid 99); 8 Oct 2007 19:09:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Oct 2007 12:09:17 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [213.205.33.54] (HELO joe.tiscali.it) (213.205.33.54) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Oct 2007 19:09:18 +0000 Received: from [192.168.0.3] (84.222.100.187) by joe.tiscali.it (7.3.122) id 46DD5017005740AB for users@myfaces.apache.org; Mon, 8 Oct 2007 21:08:56 +0200 Message-ID: <470A8079.5000607@tecnotp.it> Date: Mon, 08 Oct 2007 21:09:45 +0200 From: Renzo Tomaselli User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: MyFaces Discussion Subject: [Trinidad] how to conditionally manage detailStamp Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, as a complement to my previous message (I apologize for the missing subject), I'm looking for a way to selectively render a table with/without details. I have a table with details always enabled. Each row in turn can expand to another table, where details should be enabled only if there is anything to show. Enabling details handling on a per-row basis would be the best. Furthermore, if no row has details, I would skip the entire "show" column. The only way seems facet-driven, which prevents any chance to choose on a bean-provided getter basis. Using setDetailStamp(null) on the component as achieved by binding doesn't work either, since binding setter is invoked at compile time, when there is no current row yet to get/set. Any suggestion is welcome. -- Renzo