Return-Path: Delivered-To: apmail-myfaces-users-archive@www.apache.org Received: (qmail 67506 invoked from network); 5 Feb 2007 18:04:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Feb 2007 18:04:01 -0000 Received: (qmail 51137 invoked by uid 500); 5 Feb 2007 18:04:03 -0000 Delivered-To: apmail-myfaces-users-archive@myfaces.apache.org Received: (qmail 51101 invoked by uid 500); 5 Feb 2007 18:04:03 -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 51090 invoked by uid 99); 5 Feb 2007 18:04:03 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Feb 2007 10:04:03 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS X-Spam-Check-By: apache.org Received-SPF: neutral (herse.apache.org: local policy) Received: from [213.205.33.55] (HELO averell.tiscali.it) (213.205.33.55) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Feb 2007 10:03:53 -0800 Received: from [192.168.0.3] (84.223.105.21) by averell.tiscali.it (7.2.079) id 458977D00049FB7B for users@myfaces.apache.org; Mon, 5 Feb 2007 19:03:30 +0100 Message-ID: <45C77174.50802@tecnotp.it> Date: Mon, 05 Feb 2007 19:03:32 +0100 From: Renzo Tomaselli User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: MyFaces Discussion Subject: [Myfaces] how to sync t:saveState with refreshed restore_view phase Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, I'm using t:saveState to persist a component/bean name pair across requests. Component inclusion occurs dynamically - according to the selected tab of a tabbed panel - by means of Facelets ui:include. Troubles occur while hitting the browser refresh button, since the restored view is older than what saveState contents state. While this refresh issue is a well known effect of JSF - I wonder about any way to invalidate/sync saveState contents. In case of dynamic inclusion, this mismatch leads to component/bean misalignement, since the restored view pretends to hold a component possibly different than restored state. I could even redirect a detected refresh to a stable page, but unfortunately view restoring occurs at the very beginning of the life-cycle. Or even better - I might force the view to be rebuilt from scratch - but I don't know how. Thanks for any help -- Renzo