auron wrote:
Sorry to be the wicket newbie, but I was wondering if you guys could help me
to understand how Links work.
I understand that when you do Link(SomePage.class), it calls the zero param
constructor of SomePage, and when you do Link(new SomePage(someParams)) you
can call other constru
boolean loggedIn = session.get().isSignedIn();
MySignInForm.setVisible(!loggedIn);
then you can set your expired page settings to point to the page with your
SignInForm
hope this assists your design decision
why should you invalidate a session by passing parameter to another page
why not just
Hey Igor -
Thanks for the reply. Unfortunately I am still having some trouble finding
the solution for this. I've been using nabble to search the forums and so
far I cannot find anything of use (perhaps my search terms aren't
effective).
it seems that main problem is that when invalidating a s
search the archives for this. this is a common mistake and has been
explained/corrected on this mailing list a multitude of times.
-igor
On 11/2/07, auron <[EMAIL PROTECTED]> wrote:
>
> Hey all,
>
> Sorry to be the wicket newbie, but I was wondering if you guys could help me
> to understand how L
Hey all,
Sorry to be the wicket newbie, but I was wondering if you guys could help me
to understand how Links work.
I understand that when you do Link(SomePage.class), it calls the zero param
constructor of SomePage, and when you do Link(new SomePage(someParams)) you
can call other constructor
