Title: Message

Thanks, Faintan

 

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 with 4-5 pages.

+ Also one more issue not sure why, when I implemented interface StateHolder for my request managed-bean and try to  do this: <t:saveState id=”someId” value=”#{myBean1}” /> methods saveState and restoreState even didn’t called.

 

Thanks,

Yura.


From: Conway. Fintan (IT Solutions) [mailto:[EMAIL PROTECTED]
Sent: 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 in request scope, then when you move from page1 to page2 you will lose the data in managed-bean - unless you are using t:saveState.  If you have t:saveState on page1 and page2 which references managed-bean, when you leave page1 saveState saves the state of managed-bean.  Then when you enter page2 saveState reads the state of managed-bean and restores the data saved from page1.

 

check out :

 

For another way which does not involve t:saveState, look at :

 

HTH,

 

Fintan

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: 23 March 2006 13:16
To: users@myfaces.apache.org
Subject: saveState question

Hi, All

 

I just started use component saveState from Tomahawk.

I have two pages page1 (managed-bean {#page1}) and page2 (managed-bean {#page2}). All these beans are in request scope

Is it possible to pass from page1 data {#page1.mapping} to page2 ?

 

Thanks for any help,

Yura.



* ** *** ** * ** *** ** * ** *** ** *
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed.
Any views or opinions presented are solely those of the author, and do not necessarily represent those of ESB.
If you have received this email in error please notify the sender.

Although ESB scans e-mail and attachments for viruses, it does not guarantee
that either are virus-free and accepts no liability for any damage sustained
as a result of viruses.

* ** *** ** * ** *** ** * ** *** ** *

Reply via email to