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
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
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.
userMap is just a normal HashMap
private final MapString, String userMap = new HashMapString, String();
I wonder if his problem is caused by WASP security somehow?
Mathias P.W Nilsson wrote:
What does userMap( userName ) returns? Make sure it is an object that
implements serializable.
Are there any loggers in the class? When using private Logger logger =
Logger.getLogger(this.getClass());
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
I checked and everything is serializable, I tried stepping thru the code but
I don't see where in wicket is the behavior to choose the page expiration
page
Mathias P.W Nilsson wrote:
Are there any loggers in the class? When using private Logger logger =
