Return-Path: Delivered-To: apmail-myfaces-users-archive@www.apache.org Received: (qmail 15346 invoked from network); 31 Aug 2007 10:17:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 31 Aug 2007 10:17:21 -0000 Received: (qmail 74455 invoked by uid 500); 31 Aug 2007 10:17:12 -0000 Delivered-To: apmail-myfaces-users-archive@myfaces.apache.org Received: (qmail 74421 invoked by uid 500); 31 Aug 2007 10:17:12 -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 74409 invoked by uid 99); 31 Aug 2007 10:17:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Aug 2007 03:17:12 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of karimoveugene@mail.ru designates 194.67.57.49 as permitted sender) Received: from [194.67.57.49] (HELO f19.mail.ru) (194.67.57.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Aug 2007 10:18:10 +0000 Received: from mail by f19.mail.ru with local id 1IR3YV-000PXs-00 for users@myfaces.apache.org; Fri, 31 Aug 2007 14:16:47 +0400 Received: from [195.144.253.10] by win.mail.ru with HTTP; Fri, 31 Aug 2007 14:16:47 +0400 From: Evgeniy Karimov To: MyFaces Discussion Subject: =?windows-1251?Q?Re=3A_Tomahawk_Savestate_strange_behaviour?= Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: unknown via proxy [195.144.253.10] Date: Fri, 31 Aug 2007 14:16:47 +0400 In-Reply-To: References: Reply-To: Evgeniy Karimov Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: 8bit Message-Id: X-Virus-Checked: Checked by ClamAV on apache.org As it seems, the problem is described as a feature in comments in tomahawk source code: --- * Note that the saved object can be "chained" from view to view * in order to extend its lifetime from a single view to a sequence * of views if desired. A UISaveState component with an EL expression * such as "#{someBean}" will save the object state after render, and * restore it on postback. If navigation occurs to some other view * and that view has a UISaveState component with the same EL expression * then the object will simply be saved into the new view, thus extending * its lifetime. Seems when I reload same page in another instance of browser, JSP thinks that it's another view with same binding expression available, and restores same object, which I want to cancel. Is it possible in any way? -----Original Message----- From: ������� ������� To: users@myfaces.apache.org Date: Fri, 31 Aug 2007 12:50:52 +0400 Subject: Tomahawk Savestate strange behaviour > > Hi, I have some question about Tomahawk Savestate component: > > I create a simple for with 3 input boxes, and 1 submit button. I bind their values to some backBean, which is marked as "request" scope. > And I have > > tag. > > Before I added saveState tag, when I reopen a page in same browser - the values of bean (and corresponding component values) were new (empty), after I added saveState tag - backBean started to behave as Session bean, not as "view" scope bean... I mean it shouldn't persist through different queries, right? > Thanks in advance. >