First of all I want to state that I´m not 100% sure this is a Wicket problem but the only way I have found (so far) to reproduce it, using static HTML, is by means of the Wicket.replaceOuterHtml JS function.
The problem appears while trying to replace components containing jQuery droppables via wicket AJAX. After AJAX replacement draggables stop working with an error on jquery-1.4.2.js.
The steps I have followed so far are:
1-File the issue http://dev.jqueryui.com/ticket/5374 and attach a Wicket application showing the behavior (see quickStart http://wijqgrid.googlecode.com/svn/wiki/dragdrop.zip).
2-Post a message to the jquery forum http://forum.jquery.com/topic/drag-and-drop-problems-after-ajax-refresh-on-ie. Developers asked me for a simplified example (no Wicket involved). After some messing around I was able to reproduce this using Wicket.replaceOuterHtml function (the test case can be found here http://dev.jqueryui.com/raw-attachment/ticket/5374/testdragDrop.zip).
As said I´m not sure this is a Wicket problem as the error occurs on a jquery file... but I can´t reproduce this using jquery alone. In IMHO this is a serious limitation in using jQuery in combination with Wicket. This error affects both current Wicket-jQuery integrations: jWicket (which has opted to patch jquery to get it working) and WiQuery. Can someone of the Wicket team take a look to this, please, and confirm if this is a jquery problem?
Thanks in advance!