I've I may Add. I messed around with t:saveState about 4 months ago but for some reason it did not seem to work with my configuration of the SUN RI 1.1.x and SERVER STATE saving. I ended up abandoning it in preference for saving objects in session using a phase listerner to clean it up according to associated viewId's and various other rules.
In this case adding the t:saveState tag to 1-N other pages that the user accesses during the edit process seems like it might be a pain as the majority of time those other views are not concerned with the is edit activity. My home grown processes also seems like I'm hitting it's limit as it's built for a known predefined list of views (say 1-5) as opposed to 15 or possible 20 (volitile) other views that need to ensure the original view remains in scope. Nenz wrote: > > Hello, Sorry in advance for the possibly naive question. > > My Envionment. > > SUN RI 1.1_02 > Tomahawk 1.5 > Server State Saving. > > I have the following scenario... > > User performs a search using a number of drop downs / text inputs..etc. > ... a datatable displays the results at the bottom of the save view. User > selects a particular row in the datatable and is brought to a summary view > to edit the details of the selected row. This summary view allows the > user to bounce around the app editing pieces and parts of the summary > view.. User can cancel the edit action / or confirm the edit action. > > User is brought back to the view with the previous search criteria (drop > downs) text inputs.... restored to the point when they left the view and > the search data is also redisplayed and must reflect if the status of the > record was updated. > > I'd like an easy way to be able to return to the original view's state.. > ie.. drop down options. selected option.. input values.. etc.. without > having to save all the lists and primitive wrappers that back this view > seperately. ie. I could put a bean in session (using various state > maintenance strategies) that wraps all the pieces and parts but if I add > something new to the JSP I then need to modify this bean wrapper also. I'd > rather not have to run all the logic once again to retore the search > critieria as the drop down logic is rather involved and not subject to > change from the time they left the view originally. > > Can I simply save a reference to the entire view as faces would say on a > validation error and then after I'm completed with the edit activities and > redirect back to search.. restore the saved search view and then manually > trigger the search again with the restored criteria? > > Not sure if this makes sense but it's a problem I'm currently struggeling > with. I'm pretty familiar with JSF and have been working with it for a > solid year but would like to take it to the next level. > > Thanks! > > > > -- View this message in context: http://www.nabble.com/Save---restore-state-of-entire-view--tf2443158.html#a6812377 Sent from the MyFaces - Users mailing list archive at Nabble.com.
