Thanks Michael.
Erik.
Michael Mosmann wrote:
Hope this code will make something clear.
mm:)
--
Erik van Oosten
http://day-to-day-stuff.blogspot.com/
Am Sonntag, den 29.11.2009, 20:15 +0100 schrieb Erik van Oosten:
> Michael,
>
> What kind of container are you referring to?
public class MyUserSession implements Serializable
{
/* hold user relevant stuff */
}
public class MyWicketSession extends WebSession
{
MyUserSession _container=new M
if you never want sessions to invalidate then just have an ajax timer
that polls the server just before your container time out like 29
minutes if the time out is 30
On 19/11/2009, Hawk Newton i wrote:
> Hello Wicket folx.
>
> First and foremost I want to commend you on an excellent job putting
>
Michael,
What kind of container are you referring to? And which session, the
servlet session or the Wicket session?
Regards,
Erik.
Michael Mosmann wrote:
Hi,
I've got a business requirement that session invalidation must not be a disruptive event
(no "expired session" warning or an
Hehe, nice one. Never thought of that.
regards Nino
2009/11/20 Michael Mosmann
> Hi,
>
> > I've got a business requirement that session invalidation must not be a
> disruptive event (no "expired session" warning or anything similar).
>
> Is session invalidation an requirement? Put a container in
Hi,
> I've got a business requirement that session invalidation must not be a
> disruptive event (no "expired session" warning or anything similar).
Is session invalidation an requirement? Put a container into your
session and throw it away if you want to invalidate the "user session".
mm:)
On Nov 19, 2009, at 2:24 PM, Igor Vaynberg wrote:
> On Thu, Nov 19, 2009 at 2:15 PM, Hawk Newton wrote:
>> 2. Extend WebRequestCycle.onRuntimeException() to redirect the browser back
>> to the target page instead of the "expired session" error page. This
>> approach has the drawback that the m
On Thu, Nov 19, 2009 at 2:15 PM, Hawk Newton wrote:
> Hello Wicket folx.
>
> First and foremost I want to commend you on an excellent job putting together
> a truly impressive best-in-class framework.
>
> I'm in the process of evaluating Wicket for a large-scale ajax-heavy
> enterprise applicati
Hello Wicket folx.
First and foremost I want to commend you on an excellent job putting together a
truly impressive best-in-class framework.
I'm in the process of evaluating Wicket for a large-scale ajax-heavy enterprise
application.
I've got a business requirement that session invalidation mu