Heh, I feel a bit silly now; turns out it was a serialization error, and the
reason why it was happening at every page was because it was occurring in
the MenuHelper ^^ Thanks all!
Regards,
Ces
On Thu, Dec 10, 2009 at 12:14 PM, zlus...@gmail.com zlus...@gmail.comwrote:
Hi,
Check that
Hi all,
Currently I have a problem with my application wherein when I press the Back
button of the browser and navigate to a new page, I get a Page Expired error
consistently. However, this only happens when my application is deployed in
Glassfish, but not when I run it using Jetty. Any
make sure there are no serialization errors in your glassfish log...
-igor
On Wed, Dec 9, 2009 at 10:36 AM, Early Morning goodmorning...@gmail.com wrote:
Hi all,
Currently I have a problem with my application wherein when I press the Back
button of the browser and navigate to a new page, I
Hi,
It is usually easier to have identical development and production
platforms. If then you get an error as you describe, you usually catch
it in development before it reaches production.
So why don't you develop with GlassFish?
Bernard
On Thu, 10 Dec 2009 02:36:49 +0800, you wrote:
Hi
Well yes, ideally, but it is easier to not use such a heavy appserver when
developing, so we make do with an internal QA deployment on Glassfish :) In
any case, I was more wondering about the differences between how appservers
handle wicket page versions and the like, since I'd like to understand
Hi,
Check that session cookies are not mixed up between the application
servers. I had PageExpired exceptions when testing the same application
on the very same browser with WebLogic and Tomcat, and that was caused
by that both servers are using the JSESSIONID cookie, but with different
