• 1
• 2
• 3
• 4
• 5

accessed accesses accessing addition afterphase ajax andrei anonymous app application applications article authenticated author auto automatically autosavelistener autosavescriptjs based bean browser browserid browseridfilter build button call calls case children choose cioroianu class comp component components config configuring context contextinitialized cookie cookies copy creates ctx current data datafile datamap datamappersistence datamaprepository developer developerworks development dofilter download easy editablevalueholder environment error exception extends faces facescontext file filter final find form forms framework getbrowserid getdatamap getdatamapid header http httpservletrequest ibm id identify implement implementing implements import information input instance instances int interface java javaioserializable javascript jsf learn library limit linkedhashmap listener listing loaded managed map maps mapstring maxdatamaps memory method methods multithreaded named null number object objects obtain package page parameter part path persistence phase presented principal private processing property public rate read recursive remember repository repositorywrapper request requests resources response restore restoring retrieving return returns root safe sample save savecurrentview saved saves savevalues saving scope sctx series server services servlet servletcontext servletcontextlistener session sessions set setdatamap shown shows single site solution specification state static stop store stored storing string submit submitted synchronized techniques technology temporary thread time top tree uicomponent unique user userid users valid values view void web wrapper

Keyword Cloud Navigation Map

Introduction

Part 1 of this series describes a scenario in which your application automatically saves form data on the server and you want to be able to restore forms after your users close and reopen their browsers. The solution works even if the user's browser crashes, or if the user leaves the application without clicking Submit on the Web form.

The sample application included with this article (see Download) contains a typical JSF form named SupportForm.jsp whose data is periodically submitted to the server using the JavaScript functions of the AutoSaveScript.js file. Both SupportForm.jsp and AutoSaveScript.js are described in Part 1, which also shows how to use a JSF phase listener to process Ajax requests without interfering with the application logic.

In this article, you'll learn how to build a thread-safe data repository for keeping auto-saved form data. You'll see how to choose data structures, how to populate them with the form data extracted from the JSF component tree, how to restore the state of the JSF components, how to limit the memory resources of the data repository, and how to implement its persistence. You'll also learn several Web techniques, such as using filters and browser ID cookies.

Read Full Tutorial...