: Update ManageBean
from different pages.
t:savestate is a
good practice, also you should make your backing bean session scoped.
On 3/22/06, CONNER,
BRENDAN (SBCSI) [EMAIL PROTECTED]
wrote:
Are you using t:saveState to save
the state of the bean?
- Brendan
Avisar [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 23, 2006
1:19 PM
To: MyFaces Discussion
Subject: RE: Update ManageBean
from different pages.
Does t:saveState requires submitting the page? Cause I can see
that the data I have insert in input text in tab1 does not update the value in
my
On 3/23/06, Hagay Avisar [EMAIL PROTECTED] wrote:
Does t:saveState requires submitting the page? Cause I can see that the
data I have insert in input text in tab1 does not update the value in my
Bean….
Yes. t:saveState is a server-side process, not a javascript trick.
On 3/23/06, Hagay
Hi All,
I have a page that displays 2 tabs.
Each tab is of course another JSF page.
Meaning I have pageFrame.jsf
that displays 2 tabs, and another 2 pages page1.jsf, page2.jsf.
(One for each tab)
All pages are related to the same manage bean.
The problem is when I am navigate between
Title: Message
Are
you using t:saveState to save the state of the bean?
-
Brendan
-Original Message-From: Hagay
Avisar [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 22, 2006
12:31 PMTo: users@myfaces.apache.orgSubject: Update
ManageBean from different pages.
Hi
All
]] Sent: Wednesday, March 22, 2006
12:31 PMTo: users@myfaces.apache.orgSubject: Update
ManageBean from different pages.
Hi
All,
I have a page that displays 2
tabs.
Each tab is of course another JSF
page.
Meaning I have pageFrame.jsf
that displays 2 tabs, and another 2 pages
6 matches
Mail list logo
