Hi again,
sorry for the late response and sorry for the identation, I was quite in a
hurry yesterday.
How would I implement the same thing for 1.2.6? Where should I add code (in
the wicket classes)?
Thanks for the patience,
Konstantinos
Al Maw wrote:
Al Maw wrote:
Konstantinos:
shumbola wrote:
How to find out what was the reason for firing onbeforeunload, window
close, navigate to other place, back button, forward button, etc?
I.e. is there a way to find out the exact window close here?
No. Go write a desktop application. ;-)
Regards,
Al
--
Alastair Maw
you could write a HttpSessionListener:
in your WEB-INF:
listener
listener-classcom.my.SessionObserver/listener-class
/listener
class:
public class SessionObserver implements HttpSessionListener
{
private static final Log LOG =
Eelco Hillenius wrote:
On 6/17/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
thats not entirely correct. while the event cannot be pushed to you, you
can
pull for it. you can set a cookie with expiration null - such a cookie is
destroyed when the window is closed. so you can poll for it ad
I was looking for a wicket solution, but this is not a bad idea. I will
try this later on today and see how it goes (it does seem straightforward
enough...)
Konstantinos
Harald Gruber wrote:
you could write a HttpSessionListener:
in your WEB-INF:
listener
That won't solve your problem though. You'd get the same kind of call
back as you would get by overriding onUnbind in a custom session
store. It won't do anything for catching the event that a user closes
a browser without properly logging out.
Eelco
On 6/17/07, wicket21 [EMAIL PROTECTED] wrote:
wicket21 schrieb:
I was looking for a wicket solution, but this is not a bad idea. I will
try this later on today and see how it goes (it does seem straightforward
enough...)
probably you can implement the HttpSessionListener interface in your wicket
application and
install it
Eelco Hillenius schrieb:
That won't solve your problem though. You'd get the same kind of call
back as you would get by overriding onUnbind in a custom session
store. It won't do anything for catching the event that a user closes
a browser without properly logging out.
those methods are
Eelco Hillenius schrieb:
That won't solve your problem though. You'd get the same kind of call
back as you would get by overriding onUnbind in a custom session
store. It won't do anything for catching the event that a user closes
a browser without properly logging out.
those methods are
Yes, and the same happens for AbstractHttpSessionStore#onUnbind
ok, admit, i didnt check the source code of AbstractHttpSessionStore ;-)
so i guess, that's what he needs...
-
This SF.net email is sponsored by DB2 Express
Al Maw wrote:
Eelco Hillenius wrote:
well, I have a project where the requirement is to do some things when
user
logs out, otherwise the same user can't use the application for the next
30
minutes. It works fine when user uses the logout link, but I want the
same
behavior when the user
though it implements the HttpSessionBindingListener and not the
HttpSessionListener.
i guess the difference between both ist, that the binding listener only
realizes and observes which
values of the session are bound and the session listener recognizes if a
session itself is created
or
Konstantinos:
Firstly, please quit replying with your own text indented with a , the
same as the text you're quoting. It makes it really difficult to see
what the heck is going on. ;-)
Secondly, I said onbeforeunload, not onunload.
Al
--
Alastair Maw
Wicket-biased blog at
Al Maw wrote:
Konstantinos:
Firstly, please quit replying with your own text indented with a , the
same as the text you're quoting. It makes it really difficult to see
what the heck is going on. ;-)
Secondly, I said onbeforeunload, not onunload.
I've just added this functionality to
On Monday 18 June 2007 2:19 am, Eelco Hillenius escreveu:
Eelco Hillenius schrieb:
That won't solve your problem though. You'd get the same kind of call
back as you would get by overriding onUnbind in a custom session
store. It won't do anything for catching the event that a user closes
Çäðàâñòâóéòå, Al.
Âû ïèñàëè Monday, June 18, 2007, 3:08:44 PM:
Al Maw wrote:
Konstantinos:
Firstly, please quit replying with your own text indented with a , the
same as the text you're quoting. It makes it really difficult to see
what the heck is going on. ;-)
Secondly, I said
though it implements the HttpSessionBindingListener and not the
HttpSessionListener.
i guess the difference between both ist, that the binding listener only
realizes and observes which
values of the session are bound and the session listener recognizes if a
session itself is created
or
hi,
will this work when the user clicks the browser's close button as well?
Konstantinos
Ken Leung-2 wrote:
yes, looks like it does. thx, i 'll give it a try.
On 6/15/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
Not sure from the top of my head (don't have the project checked
well, I have a project where the requirement is to do some things when user
logs out, otherwise the same user can't use the application for the next 30
minutes. It works fine when user uses the logout link, but I want the same
behavior when the user closes the window. Any hints how to do this?
well, I have a project where the requirement is to do some things when user
logs out, otherwise the same user can't use the application for the next 30
minutes. It works fine when user uses the logout link, but I want the same
behavior when the user closes the window. Any hints how to do this?
thats not entirely correct. while the event cannot be pushed to you, you can
pull for it. you can set a cookie with expiration null - such a cookie is
destroyed when the window is closed. so you can poll for it ad if its gone
you know its a new window being opened. in the same manner you can use
On 6/17/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
thats not entirely correct. while the event cannot be pushed to you, you can
pull for it. you can set a cookie with expiration null - such a cookie is
destroyed when the window is closed. so you can poll for it ad if its gone
you know its a
Eelco Hillenius wrote:
well, I have a project where the requirement is to do some things when user
logs out, otherwise the same user can't use the application for the next 30
minutes. It works fine when user uses the logout link, but I want the same
behavior when the user closes the window.
Is there a way to trap the http session expires so that I can do some of my
own house keeping stuff in my application ?
thx
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2
Yep. In Wicket 1.3 the default session store implementations have
#onUnbind which should be called automatically with either an expiry
or an explicit invalidation. If you don't extend from the abstract
session store class (AbstractHttpSessionStore), you have to implement
something yourself.
Eelco
sounds good, but can it be done in 1.2.6 ?
thx
On 6/15/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
Yep. In Wicket 1.3 the default session store implementations have
#onUnbind which should be called automatically with either an expiry
or an explicit invalidation. If you don't extend from
Not sure from the top of my head (don't have the project checked out
here), but I think so... if the HttpSessionStore (the default in
Wicket 1.2) has onUnbind, it should do that.
Eelco
On 6/15/07, Ken Leung [EMAIL PROTECTED] wrote:
sounds good, but can it be done in 1.2.6 ?
thx
On
yes, looks like it does. thx, i 'll give it a try.
On 6/15/07, Eelco Hillenius [EMAIL PROTECTED] wrote:
Not sure from the top of my head (don't have the project checked out
here), but I think so... if the HttpSessionStore (the default in
Wicket 1.2) has onUnbind, it should do that.
Eelco
28 matches
Mail list logo
