Thanks Gwyn.
I already added the configuration to the wiki that works on WAS.
Cheers,
On 11/9/07, Gwyn Evans [EMAIL PROTECTED] wrote:
Well, there are certainly advantages to using WicketFilter, so it
might well be deprecated, but I wouldn't expect it to be removed,
which would be the real
On Nov 8, 2007 11:46 PM, Joshua Jackson [EMAIL PROTECTED] wrote:
Darn it doesn't work. I guess this is a problem with Websphere :(
Igor was referring to putting something like:
session-config
session-timeout60/session-timeout
/session-config
somewhere at the end
Thanks Eelco. I already did that.
It worked with StatelessLink and StatelessForm. Anyway is there any
issue if we use WicketServlet instead of WicketFilter as such:
servlet
servlet-namewicket.wicket/servlet-name
Hi Joshua,
One point to note might be that the 'traditional' Wicket advice for
using a Servlet mapping was not to use the root context /* but
rather use a sub mapping, e.g. /app/*, which leaves you with the
option of having static files not having to be served by Wicket. You
can always put a
And in addition, currently we prefer to use the WicketFilter in favor
of the WicketServlet precisely for this reason (wicket 1.3 only)
Martijn
On 11/9/07, Gwyn Evans [EMAIL PROTECTED] wrote:
Hi Joshua,
One point to note might be that the 'traditional' Wicket advice for
using a Servlet
On 11/9/07, Gwyn Evans [EMAIL PROTECTED] wrote:
Hi Joshua,
One point to note might be that the 'traditional' Wicket advice for
using a Servlet mapping was not to use the root context /* but
rather use a sub mapping, e.g. /app/*, which leaves you with the
option of having static files not
I know :(
But somehow I must use WicketServlet because:
1. Spring ContextLoaderListener doesn't work in WAS 5
2. The workaround is to use ContextLoaderServlet
3. If I use WicketFilter, it gets loaded first before
ContextLoaderServlet - This will cause an exception from Spring :(
I hope
extend your webapp's session timeout?
-igor
On Nov 8, 2007 9:23 PM, Joshua Jackson [EMAIL PROTECTED] wrote:
Dear all,
What is the workaround so my request is not expired?
I got this exception when clicking the Link component not long after
the application is loaded:
--
Page Expired
Sorry Igor,
But how do I do this in my WebApplication class?
Thanks
On 11/9/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
extend your webapp's session timeout?
-igor
--
What you want today, may not exist tommorrow
Blog: http://joshuajava.wordpress.com/
this is part of servlet config, youd do it in web.xml
-igor
On Nov 8, 2007 10:12 PM, Joshua Jackson [EMAIL PROTECTED] wrote:
Sorry Igor,
But how do I do this in my WebApplication class?
Thanks
On 11/9/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
extend your webapp's session timeout?
OK Igor. Sorry, I though I write it in my WebApplication class :)
Thanks
On 11/9/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
this is part of servlet config, youd do it in web.xml
-igor
--
What you want today, may not exist tommorrow
Blog: http://joshuajava.wordpress.com/
11 matches
Mail list logo
