Re: Getting Page Expired in Glassfish but not in Jetty

2009-12-10 Thread Early Morning
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

Getting Page Expired in Glassfish but not in Jetty

2009-12-09 Thread Early Morning
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

Re: Getting Page Expired in Glassfish but not in Jetty

2009-12-09 Thread Igor Vaynberg
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

Re: Getting Page Expired in Glassfish but not in Jetty

2009-12-09 Thread bht
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

Re: Getting Page Expired in Glassfish but not in Jetty

2009-12-09 Thread Early Morning
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

Re: Getting Page Expired in Glassfish but not in Jetty

2009-12-09 Thread zlus...@gmail.com
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

getting page expired

2008-12-09 Thread novotny
is I keep getting page expired after being redirected and I have no idea how to turn this behavior off or where in the wicket stack it occurs. Stepping thru with the debugger it does in face go thru the HomePage before ultimately resulting in page expired. Here is the code below, it is using Swarm

Re: getting page expired

2008-12-09 Thread Mathias P.W Nilsson
What does userMap( userName ) returns? Make sure it is an object that implements serializable. -- View this message in context: http://www.nabble.com/getting-page-expired-tp20921513p20923466.html Sent from the Wicket - User mailing list archive at Nabble.com

Re: getting page expired

2008-12-09 Thread novotny
. -- View this message in context: http://www.nabble.com/getting-page-expired-tp20921513p20923527.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional

Re: getting page expired

2008-12-09 Thread Mathias P.W Nilsson
that can help you. -- View this message in context: http://www.nabble.com/getting-page-expired-tp20921513p20923599.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED

Re: getting page expired

2008-12-09 Thread novotny
()); this might cause pag expired. If it is contained in a wicket web page. At least I know some of my collegues has got this a while ago. I'm not familiar with WASP so there might be someone else that can help you. -- View this message in context: http://www.nabble.com/getting-page-expired