Return-Path: Delivered-To: apmail-myfaces-users-archive@www.apache.org Received: (qmail 81937 invoked from network); 21 Jun 2009 02:29:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 21 Jun 2009 02:29:25 -0000 Received: (qmail 88844 invoked by uid 500); 21 Jun 2009 02:29:35 -0000 Delivered-To: apmail-myfaces-users-archive@myfaces.apache.org Received: (qmail 88756 invoked by uid 500); 21 Jun 2009 02:29:35 -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 88748 invoked by uid 99); 21 Jun 2009 02:29:34 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 21 Jun 2009 02:29:34 +0000 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=HTML_MESSAGE,SPF_PASS,SUBJECT_FUZZY_TION X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [66.163.179.132] (HELO web35508.mail.mud.yahoo.com) (66.163.179.132) by apache.org (qpsmtpd/0.29) with SMTP; Sun, 21 Jun 2009 02:29:24 +0000 Received: (qmail 5776 invoked by uid 60001); 21 Jun 2009 02:29:02 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1245551342; bh=Jy//Mrcphd+TUr4Spnm/c5QWYSKDHYQftlMIU97RfsY=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=ltULJRbyFOuxPV/wHPPuuHQg2+r7Q/MyYTQiTJFzmip/bhBRZsTM6FDnAtXhHDVygety6ItuGM1vI5zx9wS7V6J+5zHHXgm+e+35k14dPtioSWDkFzkXQZJZ+n1gyfWf6KD95EVZ1c9bCmo5b/uAxtaOniS/8cMoSpVT1CjlPfQ= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=IY52mL7VOv3pCocdVqpdgvU8IfgnfCsXY6SQq2TLdqrIwmLvy9UBHzdFyW1Mf0e4vq2BzfLJ44rWQEhVgQhsjQ/NP/b7LLU2aZB1WykaiPkGoBSEepPNbxwxQLDl9Kn0n177plXrjw1XXeWZogNkLoaCpwEyCg6BYhRXXV3I4mI=; Message-ID: <415876.3167.qm@web35508.mail.mud.yahoo.com> X-YMail-OSG: yob.K80VM1laHAA75d4fNYja5StscFhW8D4aCEY8NSM.eMLVT_dxRluU.0mo5PAiMOy0HAJFZBuDdacVi6B6857W1jPE1ApVo6NjI717kZXHMW9nlTkXtqG4QkgI0dpR5t_V.Iuduf1im94bthb1km4qnkW2ay7kGwweHai7nJvVY2Lcf6mxpJyIpyD0HqTEiFM95.2UdeUuR55RFqKDvjhwsjRXpcFxUkhJ_SYzEcKB9Ao.pZ7ew0mvMgqEeM9Uv8Kt1pIXXqp8WIWHLJasc1L8MlTXqjlCrNw9HYhFkrfMQ6VGkF8omw-- Received: from [222.65.128.251] by web35508.mail.mud.yahoo.com via HTTP; Sat, 20 Jun 2009 19:29:02 PDT X-Mailer: YahooMailClassic/5.4.17 YahooMailWebService/0.7.289.15 Date: Sat, 20 Jun 2009 19:29:02 -0700 (PDT) From: Dave Subject: [trinidad] does not support browser back button To: users@myfaces.apache.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-808165487-1245551342=:3167" X-Virus-Checked: Checked by ClamAV on apache.org --0-808165487-1245551342=:3167 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable When we use jsf ri and tomahawk, our jsf app works well for browser back bu= tton. But after we use Trinidad, browser back button does not=A0work. Consi= der the following senario: =A0 1. show a table of employees (backing bean data is a list of employees) 2. click an employee A and show the employee,(backing bean data=A0is now=A0= changed to=A0the employee) 3. click browser back button 4. click an employee=A0B.=A0 Employee B will not be shown because the backi= ng data has been changed to employee A in stop 2. =A0 I looked the generated HTML viewState values in the steps above. They are= =A0 the same. That means that only the same view(stored view tree in server= side) is used. For jsf/tomahawk, I believe different view=A0 trees are use= d for the senario above and thus back button works. =A0 Is there a config parameter for trinidad to support back button? Back button is often used by users, it is nice if we can do that with Trini= dad. =A0 Thanks, Dave=0A=0A=0A --0-808165487-1245551342=:3167 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
When we use jsf ri and tomahawk, our jsf= app works well for browser back button. But after we use Trinidad, browser= back button does not work. Consider the following senario:
 
1. show a table of employees (backing bean data is a list of employees= )
2. click an employee A and show the employee,(backing bean data i= s now changed to the employee)
3. click browser back button
4. click an employee B.  Employee B will not be shown becaus= e the backing data has been changed to employee A in stop 2.
 
I looked the generated HTML viewState values in the steps above. They = are  the same. That means that only the same view(stored view tree in = server side) is used. For jsf/tomahawk, I believe different view  tree= s are used for the senario above and thus back button works.
 
Is there a config parameter for trinidad to support back button?
Back button is often used by users, it is nice if we can do that with = Trinidad.
 
Thanks,
Dave

=0A=0A=0A=0A --0-808165487-1245551342=:3167--