use session's metadata facility to store the state. if you have a lot of these components you can store a map<key,value> under a single metadata key, just remember to make that code threadsafe.
-igor On Mon, Sep 12, 2011 at 4:02 PM, Nelson Segura <[email protected]> wrote: > Hello, > > Our app has several components that "retain" their state during a user > session. Examples like: > > 1. Number of results per page in a pageable component. > 2. State of a collapsible container. > 3. Which tab is selected in a tabbed panel. > > In old JSP world this will be tracked in the user session as an > attribute with the page name + the component id. This attribute has a > default value if not present. > What is the recommended way to handle this in the new Wicket World? > Does anyone have any experience handle similar problems? I was > planning to integrate this in the components themselves so they would > be transparent to the developer using the components. (Still using > wicket 1.4.x) > > -Nelson Segura > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
