I have updated to 6.12 (without any pane, fantastic... I cannot believe
that it was so easy)
Thanks a lot now it works
Cheers
Dirk
Am 16.11.2013 14:05, schrieb Francois Meillet:
> Update to the 6.12 version or follow Ernesto's advice or write your own
> HttpSessionStore.
>
> François Meillet
Update to the 6.12 version or follow Ernesto's advice or write your own
HttpSessionStore.
François Meillet
Formation Wicket - Développement Wicket
Le 16 nov. 2013 à 13:17, Dirk Wichmann a écrit :
> sorry, there is no methode onInvalidate() to overwrite??
>
> not in AuthenticatedWebSessio
sorry, there is no methode onInvalidate() to overwrite??
not in AuthenticatedWebSession or WebSession or in Session (I use Wicket
6.1)
Am 16.11.2013 12:47, schrieb Francois Meillet:
> In this case, override the onInvalidate() method in your custom session.
>
> from the api :
> onInvalidate is a
In this case, override the onInvalidate() method in your custom session.
from the api :
onInvalidate is a callback method that is executed when the user session is
invalidated
either by explicit call to {@link org.apache.wicket.Session#invalidate()}
or due to HttpSession expiration.
François M
Maybe bind sessionId with user ID when session is created? on a persistence
storage? So that you can recover user ID with the session Id
On Sat, Nov 16, 2013 at 12:19 PM, Dirk Wichmann wrote:
> Thanks, that works, but how can I get my WebSession Object??
> In there the user is stored and I need
Thanks, that works, but how can I get my WebSession Object??
In there the user is stored and I need the id of the user.
WebSession.get() does not work
Thanks in advance
Dirk
Am 16.11.2013 11:04, schrieb Francois Meillet:
> You can write a unboundListener and register it in your sessionStore.
> T
You can write a unboundListener and register it in your sessionStore.
This code should be in your application init()
getSessionStore().registerUnboundListener( new ISessionStore.UnboundListener() {
@Override
public void sessionUnbound(String sessionId) {
// logout t
Hi all,
it's quite frustrating, a simple thing gets complicated.
I have a Webapp with login page and logout button.
If the user clicks the logout I write a logout timestamp in the database.
Now I want to write the same timestamp when the session expires.
Only thing I have found on the Web is to us
Hi,
Servlet APIs provides
http://docs.oracle.com/javaee/6/api/javax/servlet/http/HttpSessionListener.html#sessionDestroyed(javax.servlet.http.HttpSessionEvent)
>From the passed event you can get the HttpSession. One of the attributes
inside is the Wicket Session.
On Mon, Nov 12, 2012 at 10:32 PM
Martin G put together a Session#onInvalidate() callback for this, but it
didn't receive much interest. See
https://issues.apache.org/jira/browse/WICKET-
On Mon, Nov 12, 2012 at 8:32 PM, Corbin, James wrote:
> Is there any way in Wicket 6+ to be notified when the session is ABOUT to
> be destr
Is there any way in Wicket 6+ to be notified when the session is ABOUT to be
destroyed? The UnboundListener.sessionUnbound(…) API is too late in the cycle
for me to interact with the session state.
Thanks,
J.D.
If that bookmarkable uri is a stateless page, will that prevent a new
session from being established? (Assuming the default session store is in
use)
On Dec 3, 2010 10:14 PM, "Igor Vaynberg" wrote:
> it is a good idea to always redirect to a bookmarkable url after
> invalidating your session.
>
> -
maybe i misunderstood, but wouldn't removing the page from the page map be
sufficient? we do this for our confirmation pages that show sensitive data
(like temporary passwords).
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Logout-Session-destroy-on-the
Isn't this what will happen next time he tried to "visit" any page on
the server?
Ernesto
On Sat, Dec 4, 2010 at 5:13 AM, Igor Vaynberg wrote:
> it is a good idea to always redirect to a bookmarkable url after
> invalidating your session.
>
> -igor
>
> On Thu, Dec 2, 2010 at 2:08 AM, Ernesto Rei
it is a good idea to always redirect to a bookmarkable url after
invalidating your session.
-igor
On Thu, Dec 2, 2010 at 2:08 AM, Ernesto Reinaldo Barreiro
wrote:
> e.g. you could:
>
> 1-Place and AbstractDefaultAjaxBehavior on you page (e.g. to some div
> on your page). Use urlFor to generate t
e.g. you could:
1-Place and AbstractDefaultAjaxBehavior on you page (e.g. to some div
on your page). Use urlFor to generate the URL to this behavior. On
respond(AjaxRequestTarget target) {
Invalidate your session.
}
2-Make your page implement IHeaderContributor and on
public void renderHea
Hi Matt,
I see. Then maybe adding some "onDomReady" javascript to
ConfirmationPage that simply goes back to the server and invalidates
the session? Probably this can't use wicket AJAX machinery: because
that will probably will also trigger a redirect.
Regards,
Ernesto
On Thu, Dec 2, 2010 at 10:
Hi Ernesto
No that's not possible because the ConfirmationPage is *stateful* and
contains lots of information from the session/page state, so it must be
allowed to display the pre-rendered page once but after that request,
the session must be invalidated.
Thanks
Matt
On 2010-12-02 10:34, E
Matt,
Can't you just do some kind of trick so that your ConfirmationPage is
served as the home page? So that you invalidate the session but at
getHomePage() you temporarily return your ConfirmationPage?
Regards,
Ernesto
On Thu, Dec 2, 2010 at 10:06 AM, Matthias Keller
wrote:
> Hi Randy
>
> Yes
Hi Randy
Yes it appears to have something to do with that. Our app uses the
REDIRECT_BUFFER by default (we never actively configured this though)
which appears to be a sensible option for normal operation. I'm not very
familiar with the render strategies but you appear to be right: The page
i
Does the redirect to the home page happen because of Wicket's default render
strategy (REDIRECT_TO_BUFFER) that causes two requests? You invalidate
session on the first which redirects to the buffered response. When the
second request comes in expecting to get the already-rendered response, you
ge
Hi!
I am curious too. For this reason we had to build our logoutpage so
that it invalidtes session logically but not in httpsession sense.
Only clicking something from login page will do that.
But it's a hack, I would like to know what's the proper way ;)
**
Martin
2010/12/1 Matthias Keller
Hi
I've got the following problem:
After a user completes a wizard, he sees a last confirmation page
containing some data, thus it must be a stateful page called by the
following code from the wizard:
setResponsePage(new ConfirmationPage(myBean));
This ConfirmationPage must only be displayed o
thanx, that's a simple one!
2008/3/17, Johan Compagner <[EMAIL PROTECTED]>:
>
> keep track of all the sessionids that have logged in in an List that you
> keep on your Application object.
>
>
>
>
>
> On Mon, Mar 17, 2008 at 9:10 PM, Martijn Lindhout <
> [EMAIL PROTECTED]>
> wrote:
>
>
> > Hi all,
keep track of all the sessionids that have logged in in an List that you
keep on your Application object.
On Mon, Mar 17, 2008 at 9:10 PM, Martijn Lindhout <[EMAIL PROTECTED]>
wrote:
> Hi all,
>
> In my application I track the number of users logged in. When they logout,
> I
> decrement the co
Take a look at the IRequestLogger interface it provides all sorts of
statistics although not the number of authenticated users, but maybe
you can customize the SessionData class a bit to include that
information.
Maurice
On Mon, Mar 17, 2008 at 9:10 PM, Martijn Lindhout
<[EMAIL PROTECTED]> wrote:
Hi all,
In my application I track the number of users logged in. When they logout, I
decrement the count. However, not every user will do an explicit logout, so
I have to depend on the container to destroy the session.
Because not all sessions are 'logged in' sessions, I need to check wheter
the u
27 matches
Mail list logo
