method called in some other cases ? If it is just called by
> logout/onInvalidate then there is no need to check
> "isSessionInvalidated()".
Yes, mentioned cleanup method is called in few other cases as well.
I managed to avoid a call to "isSessionInvalidated()" d
A wrote:
>
>> Actually, we've bit more complex scenario I should say; we've multiple
>> webapps running on tomcat with SSO valve configured; which means logout on
>> one application kills the session on other applications and we've session
>> implementation
n
> implementation class with logout & session invalidation handling.
> In both cases logout/invalidate, we try to do some cleanup (at a high level
> both call one method), which has this check 'isSessionInvalidated()' before
> proceeding with cleanup.
>
You didn
Actually, we've bit more complex scenario I should say; we've multiple
webapps running on tomcat with SSO valve configured; which means logout on
one application kills the session on other applications and we've session
implementation class with logout & session invalidatio
Hi,
On Tue, Apr 3, 2018 at 3:24 PM, Rakesh A wrote:
> I see the ticket https://issues.apache.org/jira/browse/WICKET-6547 closed
> as
> 'resolved' with resolution 'not a problem'. Instead of reopening it I
> wanted
> to discuss the usecase here and decide on re-opening.
>
> Is is allowed to call
I see the ticket https://issues.apache.org/jira/browse/WICKET-6547 closed as
'resolved' with resolution 'not a problem'. Instead of reopening it I wanted
to discuss the usecase here and decide on re-opening.
Is is allowed to call 'Session.isSessionInvalidated()' from
'WebSession.onInvalidate()' ?
Did a quick test and logged an issue
https://issues.apache.org/jira/browse/WICKET-6547
--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.o
Wicket 6.29.0 has a fix for https://issues.apache.org/jira/browse/WICKET-6484
change-set of which can be see at -
https://git-wip-us.apache.org/repos/asf?p=wicket.git;a=blobdiff;f=wicket-core/src/main/java/org/apache/wicket/Session.java;h=21a9432a2c5d5005b215dd5d7c3b15bf87fda0ba;hp=5bab1c6bf5fd602
this case I would not depend on the session at all, if possible.
> > > Simply copy the OAuth token to a private variable in your threads.
> > >
> > > B) Instead of the threads "polling" to see if the session is still
> there,
> > > I'd turn thin
t; the threads? Do they continue (A) or do they need to stop (B)?
> >
> > A) In this case I would not depend on the session at all, if possible.
> > Simply copy the OAuth token to a private variable in your threads.
> >
> > B) Instead of the threads "polling" to see
epend on the session at all, if possible.
> Simply copy the OAuth token to a private variable in your threads.
>
> B) Instead of the threads "polling" to see if the session is still there,
> I'd turn things around. Keep track of sessions-and-their-threads somewhere.
> Reg
.
Simply copy the OAuth token to a private variable in your threads.
B) Instead of the threads "polling" to see if the session is still
there, I'd turn things around. Keep track of sessions-and-their-threads
somewhere. Register a session invalidation listener, and when the
session
Hi all,
This is maybe a Spring question but as my app is a wicket app and I use
this list regularly and everyone is very helpful I thought I'd ask here
first.
I have a RequestCycleListener which during onBeginRequest() conditionally
spawns some background threads and runs them using an Executor.
On Thu, May 28, 2009 at 11:24 AM, Johan Compagner wrote:
> why are you using invalidateNow?
>
I was using it for invalidating sessions on logout. But since plain
invalidate() works, and doesn't break RequestLogger, my original problem is
fixed.
Regards,
Taneli Korri
why are you using invalidateNow?
On Thu, May 28, 2009 at 10:11, Taneli Korri wrote:
> On Thu, May 28, 2009 at 6:49 AM, Jeremy Thomerson <
> jer...@wickettraining.com
> > wrote:
>
> > Please open a JIRA so this doesn't get lost. I haven't looked, but it
> > sounds wrong if it truly recreates an
On Thu, May 28, 2009 at 6:49 AM, Jeremy Thomerson wrote:
> Please open a JIRA so this doesn't get lost. I haven't looked, but it
> sounds wrong if it truly recreates an invalidated session in some
> end-of-request logging, even if it doesn't bind the session. Post the
> link back here.
>
>
I f
On Wed, May 27, 2009 at 8:25 AM, Taneli Korri wrote:
> Hi,
>
> I'm using Wicket 1.3.6 and RequestLogger.getLiveSessions to get the current
> sessions in my web application, but I'm experience strange behaviour when
> session invalidation occurs.
>
> When the us
Hi,
I'm using Wicket 1.3.6 and RequestLogger.getLiveSessions to get the current
sessions in my web application, but I'm experience strange behaviour when
session invalidation occurs.
When the user logs out of the application, the session is invalidated. Thi
Hi,
I have a custom session for my wicket application 1 and the custom session
has some attributes.
from wicket application 1, i navigate to wicket application 2.
And in wicket application 2, i have a custom request cycle in which retrieve
the custom session of wicket application 1 is retrieved and
empty PageParameters has being passed...
Adriano
Adriano dos Santos Fernandes escreveu:
Hi!
After upgrade from m3 to rc1, a problem with session invalidation
appeared.
I have a "Exit" menu, using Ajax (AbstractDefaultAjaxBehavior). On its
respond, it does:
getSessi
Hi!
After upgrade from m3 to rc1, a problem with session invalidation appeared.
I have a "Exit" menu, using Ajax (AbstractDefaultAjaxBehavior). On its
respond, it does:
getSession().invalidate();
setResponsePage(HomePage.class);
This worked with m3, but now nothing happens,
21 matches
Mail list logo
