Re: Hide page version query parameters

2012-01-03 Thread Taneli Korri
s with urlrewritefilter. So no more internal server errors. Regards, Taneli Korri - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org

Re: Hide page version query parameters

2012-01-02 Thread Taneli Korri
On Mon, Jan 2, 2012 at 9:47 AM, Martin Grigorov wrote: > On Mon, Jan 2, 2012 at 8:18 AM, Taneli Korri wrote: >> On Sat, Dec 31, 2011 at 4:31 PM, Martin Grigorov >> wrote: >>> On Sat, Dec 31, 2011 at 2:29 PM, Taneli Korri wrote: >>>> On Sat, Dec

Re: Hide page version query parameters

2012-01-01 Thread Taneli Korri
On Sat, Dec 31, 2011 at 4:31 PM, Martin Grigorov wrote: > On Sat, Dec 31, 2011 at 2:29 PM, Taneli Korri wrote: >> On Sat, Dec 31, 2011 at 9:09 AM, Martin Grigorov >> wrote: >>> On Fri, Dec 30, 2011 at 11:43 PM, martin.dilger >>> wrote: >>>>

Re: Hide page version query parameters

2011-12-31 Thread Taneli Korri
number was stored somewhere behind the scenes. I'm guessing this isn't possible anymore in Wicket 1.5? Regards, Taneli Korri - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org

Re: Hide page version query parameters

2011-12-28 Thread Taneli Korri
eter? I'm also trying to figure out how to achieve that in Wicket 1.5. In 1.4 it was easy since, mounting the page with mountBookmarkablePage was enough. Regards Taneli Korri -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Hide-page-version-query-parameters-tp41630

Re: RequestLogger and session invalidation

2009-05-29 Thread Taneli Korri
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

Re: RequestLogger and session invalidation

2009-05-28 Thread Taneli Korri
> link back here. > > I found out what's causing the problem, I was using Session.invalidateNow() which invalidates the session before it's logged. With Session.invalidate() the problem doesn't exist. I created a JIRA issue about it: https://issues.apache.org/jira/browse/WICKET-2291 Regards, Taneli Korri

RequestLogger and session invalidation

2009-05-27 Thread Taneli Korri
estLogger on in production environment? I'm thinking that it might hog a lot of resources, but is that the case? Regards, Taneli Korri