Re: JQuery contribution question

Hi, On Thu, May 23, 2013 at 11:21 PM, Raul ralva...@netwie.com wrote: Hello, I also need to upgrade the version of jQuery to 1.9.1, I do it with getJavaScriptLibrarySettings (). setJQueryReference (resource), but I have some problems running this version with AjaxEventBehavior. Please

Re: REDIRECT_TO_BUFFER render strategy and Wicket 6.8.0

I found the solution by myself ... mvn clean -DskipTests package does the job on my Windows system -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/REDIRECT-TO-BUFFER-render-strategy-and-Wicket-6-8-0-tp4658991p4659009.html Sent from the Users forum mailing list

RE: After upgrade to Wicket 6: lots of 'java.io.IOException: Connection reset by peer' in my logs

Hi, I'm having same errors in IE10 and Opera. Chrome and Firefox don't do this (neither does IE always, but almost always it does). Wicket versions are 1.5.8 and 6.7.0 My case is a modal window that contains a panel with Image (org.apache.wicket.markup.html.image.Image) When modal window

Re: REDIRECT_TO_BUFFER render strategy and Wicket 6.8.0

I'm still interested what failures there are on Windows. Most of us develop on Linux/Mac and our CI servers are Linux too. So we have tests failing on Windows from time to time. But usually it is a problem in the tests themselves. On Fri, May 24, 2013 at 10:38 AM, Dirk Forchel

Re: After upgrade to Wicket 6: lots of 'java.io.IOException: Connection reset by peer' in my logs

Hi, On Fri, May 24, 2013 at 10:47 AM, Mikko Pukki mikko.pu...@syncrontech.comwrote: Hi, I'm having same errors in IE10 and Opera. Chrome and Firefox don't do this (neither does IE always, but almost always it does). Wicket versions are 1.5.8 and 6.7.0 My case is a modal window that

Re: After upgrade to Wicket 6: lots of 'java.io.IOException: Connection reset by peer' in my logs

There is an open ticket in our Jira about this problem - https://issues.apache.org/jira/browse/WICKET-3869. It has a quickstart too. You may try to debug it if it reproduces with your setup. On Fri, May 24, 2013 at 11:29 AM, Martin Grigorov mgrigo...@apache.orgwrote: Hi, On Fri, May 24,

Re: REDIRECT_TO_BUFFER render strategy and Wicket 6.8.0

Hi Martin, I could pinpoint the commit which changed the behavior in our application: git.exe bisect bad 34f43642195058f375d161dbb7cec58b40711423 is the first bad commit commit 34f43642195058f375d161dbb7cec58b40711423 Author: Martin Tzvetanov Grigorov mgrigo...@apache.org Date: Fri Apr 19

Re: REDIRECT_TO_BUFFER render strategy and Wicket 6.8.0

We will need a quickstart to debug it. With this change the calculation whether a page is stateless or not is postponed to a later phase of the page lifecycle. A page has the pageId (?X) only if it is stateful. On Fri, May 24, 2013 at 1:08 PM, Dirk Forchel dirk.forc...@exedio.comwrote: Hi

Re: REDIRECT_TO_BUFFER render strategy and Wicket 6.8.0

Here the failure trace: java.lang.AssertionError at org.junit.Assert.fail(Assert.java:92) at org.junit.Assert.assertTrue(Assert.java:43) at org.junit.Assert.assertTrue(Assert.java:54) at

Problems when upgrading Jquery

Hello, I updated my application to use Jquery 1.9.1, for this I added the following to the Init method of my application class. JavaScriptResourceReference resource = new JavaScriptResourceReference( MyApplication.class,

Re: Problems when upgrading Jquery

Hi, you should check for JavaScript errors (if any) with a dev tool like FireBug. Hello, I updated my application to use Jquery 1.9.1, for this I added the following to the Init method of my application class. JavaScriptResourceReference resource = new JavaScriptResourceReference(

Re: REDIRECT_TO_BUFFER render strategy and Wicket 6.8.0

I reckon WICKET-5083 is a bugfix for wrong rendered URLs (stateful pages were rendered without a page version number) which in our case was correct but just as a mistake. It seems, that our pages are stateful and therefore get the page version number (page id ?x) attached. As I described above, in

Re: REDIRECT_TO_BUFFER render strategy and Wicket 6.8.0

On Fri, May 24, 2013 at 3:22 PM, Dirk Forchel dirk.forc...@exedio.comwrote: I reckon WICKET-5083 is a bugfix for wrong rendered URLs (stateful pages were rendered without a page version number) which in our case was correct but just as a mistake. It seems, that our pages are stateful and

dynamic form (with list + add/remove)

Hey, I was looking for a good example for creating a dynamic form with a list and add/remove functionality. I looked at the ListView, but this article from Martijn's blog tells to use a RepeatingView http://wicketinaction.com/2008/10/building-a-listeditor-form-component/ this article is from

MootipBehaviour Panel Error

http://apache-wicket.1842946.n4.nabble.com/file/n4659025/photo.png - Unable to find the markup for the component. That may be due to transparent containers or components implementing IComponentResolver: [MarkupContainer [Component id = mooTipAjaxPanel]]