On 3/23/06, [EMAIL PROTECTED]
> But I can use jsf session beans as it, because on our project we are using
> JBoss 4.0.3 in cluster and for all JSF UI components I will get
> NonSerializable exception. Also I can not use one manage bean on two pages,
> because I have actually wizard application wit
: Thursday, March 23, 2006
3:53 PM
To: MyFaces Discussion
Subject: RE: saveState question
Hi Yura,
The simplest way to pass data from page1
to page2 is to use one managed
bean, and use t:saveState on both pages referring to that one managed
bean.
If the managed-bean is
Title: Message
Hi
Yura,
The
simplest way to pass data from page1 to page2 is to use
one managed bean, and use t:saveState on both pages referring to that one managed bean.
If the
managed-bean is in request scope, then when you move from page1 to page2 you
will lose the data in managed-b
-Original Message-
> From: Tom Butler [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 06, 2006 10:45 PM
> To: 'MyFaces Discussion'; [EMAIL PROTECTED]
> Subject: RE: savestate question
>
> So you are saying that t:saveState saves state only for subsequent page
> views
Tom Butler [mailto:[EMAIL PROTECTED]
Sent: Monday, February 06, 2006 10:45 PM
To: 'MyFaces Discussion'; [EMAIL PROTECTED]
Subject: RE: savestate question
So you are saying that t:saveState saves state only for subsequent page
views for the same page such as when using t:datascroller to scr
)
* When back to page #1 using a commandbutton, backingbeanPage1 state is
restored properly
Thanks
Tom
-Original Message-
From: Martin Marinschek [mailto:[EMAIL PROTECTED]
Sent: Monday, February 06, 2006 3:24 AM
To: MyFaces Discussion
Subject: Re: savestate question
Hi Tom,
Save state
Hi Tom,
Save state means that the information is stored with the state
associated to a page. Now if you change to another page, and come back
to the first one, the state of the first page has been lost, and the
state of the saveState as well.
regards,
Martin
On 2/6/06, Tom Butler <[EMAIL PROTEC
Found the problem here. On the second
page, I also included a t:saveState tag for the backing bean from the
previous page (page that linked to second page):
I must of missed this somewhere, but also this did
not seem obvious. It seemed logical that if I used on
the first page with
Will that work even over a redirect?On 8/25/05, Mike Kienenberger <[EMAIL PROTECTED]> wrote:
As long as you navigate to a page that contains a matching x:saveStatetag, the data will be moved from your posted form data to the currentcomponent tree and be rendered back out as html again.On 8/25/05, G
As long as you navigate to a page that contains a matching x:saveState
tag, the data will be moved from your posted form data to the current
component tree and be rendered back out as html again.
On 8/25/05, Galen Dunkleberger <[EMAIL PROTECTED]> wrote:
> Am I correct in believing that the x:saveS
Duong BaTien schrieb:
Manfred Geiler wrote:
Purpose of is to save the value of the property of a
bean in request scope. It is a convenient way to preserve values
between requests when you are using client side state saving and you
do not want to use session scope beans.
If you want to save valu
Manfred Geiler wrote:
Purpose of is to save the value of the property of a
bean in request scope. It is a convenient way to preserve values
between requests when you are using client side state saving and you
do not want to use session scope beans.
If you want to save values "over a longer peri
On Mon, 31 Jan 2005 14:09:28 -0500, Sean Schofield
<[EMAIL PROTECTED]> wrote:
> > SEan,
> > do you mean ViewController-Interface?
> > http://www.apache.org/~craigmcc/struts-shale/org/apache/shale/ViewController.html
> > It also contains a nice prerender() method. That is also nice if you've
> > got
> SEan,
> do you mean ViewController-Interface?
> http://www.apache.org/~craigmcc/struts-shale/org/apache/shale/ViewController.html
> It also contains a nice prerender() method. That is also nice if you've
> got non-request scope beans.
Yup that's the one.
> -Matthias
sean
In Struts Shale there is an optional interface that you can have your
backing beans implement. This interface includes an init method
(can't remember the exact name of the method offhand) which will be
guaranteed (by Shale) to be called right after the bean is created by
the managed bean facility.
The saveState feature seems interesting. I will definitely need to
check it out. One thing I am wondering about is how this feature
might interract with something Craig is doing with Struts Shale.
In Struts Shale there is an optional interface that you can have your
backing beans implement. Th
Manfred Geiler wrote:
Purpose of is to save the value of the property of a
bean in request scope. It is a convenient way to preserve values
between requests when you are using client side state saving and you
do not want to use session scope beans.
If you want to save values "over a longer peri
Purpose of is to save the value of the property of a bean
in request scope. It is a convenient way to preserve values between
requests when you are using client side state saving and you do not want
to use session scope beans.
If you want to save values "over a longer period of time", i.e. betw
18 matches
Mail list logo
