Then i must be missing something here :s. The api doc clearly states: /** * Force binding this session to the application's * [EMAIL PROTECTED] ISessionStore session store} if not already done so. * <p> * A Wicket application can operate in a session-less mode as long as * stateless pages are used. Session objects will be then created for each * request, but they will only live for that request. You can recognize * temporary sessions by calling [EMAIL PROTECTED] #isTemporary()} which basically * checks whether the session's id is null. Hence, temporary sessions have * no session id. * </p> * <p> * By calling this method, the session will be bound (made not-temporary) if * it was not bound yet. It is useful for cases where you want to be * absolutely sure this session object will be available in next requests. * </p> * <p> * This method should not typically be called by clients * </p> */
And looking at the code (1.3) it seems to do just that. Maurice On 6/14/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
On 6/14/07, Johan Compagner <[EMAIL PROTECTED]> wrote: > he just has to call dirty() when he alters a session and wants to store it That currently (in 1.3) doesn't trigger binding. Eelco
