Hi,
i am trying to implement a simple authentization.
I've basically copied what's in the auth example #2 in wicket examples,
and have a Logout button:
add( new Link("logoutLink") {
@Override public void onClick() {
sess.invalidateNow();
> Which, when clicked, is performed, but in the second request, the User
> object, which set to null in my overriden signOut(), is back in my
when are you exactly calling signOut? cant be deduced from your
snippet and comment. Session.invalidateNow won't remove your custom
session properties by it
Hi,
You need to use Session#invalidate() actually.
#invalidate() schedules a call to #invalidateNow() at the end of the
request cycle.
By using #invalidateNow() you invalidate the current http session and
right after this your app creates a new Session because it needs to
finish the request cycl
Solved.
I was writing an original reply, using "I think I have something
conceptually wrong", when it hit my mind:
One of the components (the login/logout box) has this:
final EsscAuthSession sess = (EsscAuthSession)getSession();
and the onClick() was like
add( new Link("log
