[
https://issues.apache.org/jira/browse/WICKET-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eelco Hillenius updated WICKET-784:
-----------------------------------
See discussion here:
http://www.nabble.com/Custom-session-not-working...-tf4132685.html
I think we can summarize that we really should take a closer look at
Session#dirty again for Wicket 1.4. For now, we should check what happens when
bind is called multiple times. A check look at the code shows that it should be
streamlined a bit.
> Session.dirty() does not cause an unbound session to bind.
> ----------------------------------------------------------
>
> Key: WICKET-784
> URL: https://issues.apache.org/jira/browse/WICKET-784
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.0-beta2
> Reporter: Spencer Crissman
> Priority: Minor
> Fix For: 1.3.0-beta3
>
>
> If a subclass of WebSession calls dirty(), the session will not be stored
> unless it has previously been bound. Users must call bind() explicitly on
> the session if the application is otherwise stateless, or else the change
> being flagged by dirty() will not be persisted (a new session will be
> generated for the next request).
> The expected behavior is that when flagged as dirty() the session would cause
> itself to bind, if it wasn't already doing so.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
