I'll try disabling SiteMesh and see if it still happens.
Matt
Eelco Hillenius wrote:
>
> Using Wicket 1.3 is the surest way to get rid of it.
>
> In your case, I wouldn't be surprised if the problem can be traced
> back to the fact that you use SiteMesh with Wicket. As I understand
> it, Site
Using Wicket 1.3 is the surest way to get rid of it.
In your case, I wouldn't be surprised if the problem can be traced
back to the fact that you use SiteMesh with Wicket. As I understand
it, SiteMesh combines separate requests like working with frames would
do, correct? So for every Wicket piece
This is strange. It seems that your session is being invalidated when
you save .java or .html file. This is not normal. I don't know what
kind of magic maven jetty plugin does, i usually run my web apps with
embedded jetty as regular Java application, though I'm not sure that
this is what causes yo
I'm using Eclipse, Maven 2 and the Maven Jetty Plugin (with "mvn jetty:run")
to develop my Wicket application. Everytime I save a .java or .html file,
Jetty reloads and all is good. However, when I hit "refresh" on my browser,
Wicket allways gives me a "page expired" error and I have to start fr
