> the default behavior is for a session to be temporary? that doesnt make > sense.
It is Wicket trying to be as efficient as possible. I understand the confusion, but think of it: you would typically only want a persistent session when you actually do something with it (like setting the user). An easy solutation in your case would be to call #bind in your custom session's constructor. Can you try that and let us know whether that helped? > this maybe another reason. i have my login code (basically everything you've > seen) in an abstract BasePage class. I then call Index which extends > BasePage. would that have anything to do with anything? I don't know. Why did you decide to put that loging code in that base class? Did you take a look at the wicket-auth-roles project (an example of how you can do authorization in a nicer way than e.g. the library example does it)? Eelco ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
