On 9/21/07, hillj2 <[EMAIL PROTECTED]> wrote:
> Also are there any other issues with using HttpSessionStore besides losing
> back button support? Since I'm already forced to use ONE_PASS_RENDER (for
> now), I've already lost that support (haven't I?).
ONE_PASS_RENDER does not kill back button support, but does provoke
that blasted repost on back button for form submissions. So it
prevents the double submit problem.
The HttpSessionStore is the default store for wicket 1.2 and prior. It
only limits the number of pages that are stored per session for
backbutton support. So you will be able to press back, but not
unlimited as with the disk based store.
As for the serialization errors, somehow either you don't read the log
too well, or you have a misconfigured Wicket. To fix them, you should
return to the Disk store: it will report exactly what is wrong. Do you
run the application in development mode on your local box? If so, you
should see things like the following in your log:
ERROR - Objects - Error serializing object class wicket.in.action.HomePage
Field hierarchy is:
0 [class=wicket.in.action.HomePage, path=0]
children [class=[Lorg.apache.wicket.Component;]
children[0] [class=org.apache.wicket.markup.html.basic.Label, path=0:name]
model [class=org.apache.wicket.model.PropertyModel]
target [class=wicket.in.action.User] <----- field that is
not serializable
at org.apache.wicket.util.io.SerializableChecker.check()
at org.apache.wicket.util.io.SerializableChecker.checkFields()
Martijn
--
Buy Wicket in Action: http://manning.com/dashorst
Apache Wicket 1.3.0-beta3 is released
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
