Re: null lastPage at restoreAfterSerialization

I know this has been a while, but was this ever resolved? We're seeing the same problem. And, because of this problem, Wicket is never cleaning up old session pagemap files which leads to oodles of files in our tomcat work directory. Thanks, Meetesh On Sat, Nov 22, 2008 at 5:55 AM, Carlos Pita

Re: null lastPage at restoreAfterSerialization

at 8:47 PM, Meetesh Karia meetesh.ka...@gmail.com wrote: I know this has been a while, but was this ever resolved? We're seeing the same problem. And, because of this problem, Wicket is never cleaning up old session pagemap files which leads to oodles of files in our tomcat work directory

Language selector component available anywhere?

Hi all, I was just wondering if there's a language selector component (ie, flags, language names in a dropdown, etc) out there that someone's built. A google search didn't yield any results. Thanks, Meetesh

Ajax and isTransparentResolver

Hi all, We're seeing an issue with ajax and isTransparentResolver set to return true and I'm wondering if this is something we're doing wrong or if it's an oversight. Here's an example: add(new WebMarkupContainer(toUpdate) { @Override public boolean isTransparentResolver() {

Re: Ajax and isTransparentResolver

Thanks for the information ... I'll change our code. Meetesh Igor Vaynberg wrote: i dont think we can support transparent resolvers as ajax targets -igor On Fri, Apr 11, 2008 at 10:00 AM, Meetesh Karia [EMAIL PROTECTED] wrote: Hi all, We're seeing an issue with ajax

Bug in wicket-ajax.js introduced in Wicket 1.3.2?

Hi all, We recently upgraded to Wicket 1.3.2 from Wicket 1.3.1 and we're seeing a bug with ajax behavior in Firefox (2.0.0.13 on Windows Vista). Basically, the following header is returned from an ajax call: ?xml version=1.0 encoding=UTF-8?ajax-responseheader-contribution encoding=wicket1

Re: Bug in wicket-ajax.js introduced in Wicket 1.3.2?

Unfortunately that patch doesn't solve the problem. I've added a comment to the issue with a different patch which addresses our problem and the problem mentioned in the issue (I hope :) ). Thanks, Meetesh Thijs wrote: See https://issues.apache.org/jira/browse/WICKET-1426 Meetesh Karia

MarkupCache change in 1.3.2 breaks style/variation/locale markup support

We're running into a problem with the change made for this issue: http://issues.apache.org/jira/browse/WICKET-1370 Basically, if you have a situation like this where the Login page extends DefaultPage and uses wicket:extend: Login.html DefaultPage.html DefaultPage_style1.html

Re: MarkupCache change in 1.3.2 breaks style/variation/locale markup support

.. On Wed, Apr 9, 2008 at 8:04 PM, Meetesh Karia [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: We're running into a problem with the change made for this issue: http://issues.apache.org/jira/browse/WICKET-1370 Basically, if you have a situation like this where the Login page

Sporadic exponential explosion of session size

Hi all, We're running into a problem that we've seen happen many times though unfortunately we can't consistently reproduce it. We're using Wicket 1.3.1 with automatic multi-window support enabled and the default SecondLevelCacheSessionStore. During normal use of our site, no Pages

Re: Sporadic exponential explosion of session size

29, 2008 at 8:59 AM, Meetesh Karia [EMAIL PROTECTED] wrote: There's nothing obvious and we don't hold references between pages intentionally. Additionally, when we use the site normally (ie, without opening new tabs), we don't run into this problem (and I would expect us to if we were holding

OutOfMemoryError (not PermGen) in PageSavingThread

Hi all, We're getting an OutOfMemoryError (Wicket 1.3.1 on Tomcat 5.5.17 with Sun JVM 1.5.0_06-b05) in the PageSavingThread occasionally and I was just wondering if anyone had seen this before. Is it likely just a side-effect of some other problem in our application? Or is this an issue

Re: OutOfMemoryError (not PermGen) in PageSavingThread

increasing the limit with the same load, this shouldn't be it, though. BR, Henrik 2008/2/22, Meetesh Karia [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: Hi all, We're getting an OutOfMemoryError (Wicket 1.3.1 on Tomcat 5.5.17 with Sun JVM 1.5.0_06-b05) in the PageSavingThread

Localizer backwards incompatibility bug in 1.3?

Hi all, In Wicket 1.2.6, we created some properties files like: Foo.properties Foo_style1.properties Foo_style2.properties and used StringResourceModel to look up property values. This worked correctly as in 1.2.6, Localizer didn't cache the property lookups and respected the style.

Re: n^2 loop in MarkupContainer?

. Right now, I don't see any easy way around, are you absolutely sure that it causes you performance problems? -Matej On Feb 11, 2008 2:15 PM, Meetesh Karia [EMAIL PROTECTED] wrote: Hi all, I'm using DataView in wicket 1.3 and we have ~400 items that are returned by a data provider. I'd expect

n^2 loop in MarkupContainer?

Hi all, I'm using DataView in wicket 1.3 and we have ~400 items that are returned by a data provider. I'd expect the adding of the items to be rather quick but it turns out that it's not and it looks like the culprit might be MarkupContainer.put. That method expands the children array 1

Redirecting to bookmarkable url after change in DropDownChoice

Hi all, I'm looking for the best way (within wicket) to end up at a bookmarkable url after a change in a DropDownChoice. For example: 1. I'm at the url '/category/foo' 2. I change the category DropDownChoice to 'bar' 3. I want the user (without a manual submit) to end up at '/category/bar'

Intercept pages and support for pages opened in new windows/tabs

Happy New Year all. I'm running into a problem with the use of intercept pages together with wicket 1.2.x's support for opening pages in new tabs/windows. Basically, if someone has a tab open to our site and then opens a link in another tab which causes the user to be redirected to an