I always believe something like saveState is trick, trick is good and bad thing. You better put it at back bean, not in JSF page. JSF is for presentation, it is bad keep some data handling logic in JSF page.

Also another thing, how can I get the object(instance) of myBean at back, in Swing, we have varibale name, how could page know which instance used in which page?!. We have lots things if we use saveState.

On 9/1/05, CONNER, BRENDAN (SBCSI) <[EMAIL PROTECTED] > wrote:
You say <t:saveState value="#{myBean}"/> on every page that needs your bean saved.  (That's another reason why I keep my data beans separate from my action beans; there's no sense in saving my methods.)
 
- Brendan
-----Original Message-----
From: Zhong Li [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 01, 2005 4:56 PM
To: MyFaces Discussion
Subject: Re: more on architecture really confused on something (shocker:)

Also something let us go back to Swing, the super model for JSF. dataModels in Swing you can use it as long as you needs, but this isn't case in JSF. If we want keep same thing in JSF, we have to have a way to allow use to define a dataModel, give it a "datamodel scope", so user can create one when they need it, destory it when they want to do. But how to do it easily in saveState?

Reply via email to