the problem with session data is just tricky, if you have a shopping
basket that is stored in the session object, and you add some to it,
the remove a few, then use the back button. what you now see on the
screen is the full shopping basket again, but on the serverside a
previos page is restored, so the view shows everything but the data
not, if you then remove one you have very funny behavior which you
really have to program for.
On 7/11/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> this is not really solveable by wicket itself.
> We don't know where such a reference is comming from, so this should be
> documented i guess
> that if you use session data from the session object itself. You should
> always use an extra
> indiretion to get it
> new Model()
> {
> getObject() {Session.get().getList()}
> }
I don't see a generic solution either, but in this case I though you
should use custom serialization of either your custom session or a
model you use for the extra indirection.
Eelco
