svn commit: r926476 [2/2] - in /wicket/trunk: wicket-examples/.settings/ wicket-extensions/src/main/java/org/apache/wicket/extensions/ajax/markup/html/ wicket-extensions/src/main/java/org/apache/wicke
Modified:
wicket/trunk/wicket/src/main/java/org/apache/wicket/markup/renderStrategy/DeepChildFirstVisitor.java
URL:
http://svn.apache.org/viewvc/wicket/trunk/wicket/src/main/java/org/apache/wicket/markup/renderStrategy/DeepChildFirstVisitor.java?rev=926476&r1=926475&r2=926476&view=diff
==
---
wicket/trunk/wicket/src/main/java/org/apache/wicket/markup/renderStrategy/DeepChildFirstVisitor.java
(original)
+++
wicket/trunk/wicket/src/main/java/org/apache/wicket/markup/renderStrategy/DeepChildFirstVisitor.java
Tue Mar 23 06:56:28 2010
@@ -1,174 +1,173 @@
-/*
- * Licensed to the Apache Software Foundation (ASF) under one or more
- * contributor license agreements. See the NOTICE file distributed with
- * this work for additional information regarding copyright ownership.
- * The ASF licenses this file to You under the Apache License, Version 2.0
- * (the "License"); you may not use this file except in compliance with
- * the License. You may obtain a copy of the License at
- *
- * http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- */
-package org.apache.wicket.markup.renderStrategy;
-
-import org.apache.wicket.Component;
-import org.apache.wicket.MarkupContainer;
-import org.apache.wicket.Component.IVisitor;
-import org.apache.wicket.util.lang.Checks;
-
-/**
- *
- * @author Juergen Donnerstag
- */
-public abstract class DeepChildFirstVisitor implements IVisitor
-{
- /**
-* Construct.
-*/
- public DeepChildFirstVisitor()
- {
- }
-
- /**
-* Render the child hierarchy headers.
-*
-* @param rootComponent
-* @return The object return by component()
-*/
- public final Object visit(final Component rootComponent)
- {
- Checks.argumentNotNull(rootComponent, "rootComponent");
-
- if (rootComponent instanceof MarkupContainer)
- {
- final Component[] lastComponent = new Component[1];
- Object rtn =
((MarkupContainer)rootComponent).visitChildren(new
Component.IVisitor()
- {
- public Object component(Component component)
- {
- // skip invisible components
- if (component.isVisibleInHierarchy())
- {
- // In case it is a 'leaf'
component, than ...
- if (!(component instanceof
MarkupContainer) ||
-
((MarkupContainer)component).size() == 0)
- {
- // Lets assume we
rendered the 1st leaf already and we now reached
- // the 2nd leaf. If the
2nd leave has the very same parent, than we
- // don't do anything.
If not, than we need to render the 1st component's
- // parents until such a
parent is equal to the 2nd component parent.
- if (lastComponent[0] !=
null)
- {
- MarkupContainer
parent = lastComponent[0].getParent();
- while ((parent
!= null) && (parent != rootComponent) &&
-
isCommonParent(parent, lastComponent[0], component) == false)
- {
- //
Render the container since all its children have been
- //
rendered by now
- Object
rtn = component(parent);
-
- // If
visitor returns a non-null value, it halts the traversal
- if
((rtn != IVisitor.CONTINUE_TRAVERSAL) &&
-
(rtn != IVisitor.CONTINUE_TRAVERSAL_BUT_DONT_GO_DEEPER))
-
svn commit: r926464 - /wicket/branches/wicket-1.4.x/wicket/src/test/java/org/apache/wicket/VisitorTest.java
Author: ivaynberg
Date: Tue Mar 23 05:23:58 2010
New Revision: 926464
URL: http://svn.apache.org/viewvc?rev=926464&view=rev
Log:
a more comprehensive test
Modified:
wicket/branches/wicket-1.4.x/wicket/src/test/java/org/apache/wicket/VisitorTest.java
Modified:
wicket/branches/wicket-1.4.x/wicket/src/test/java/org/apache/wicket/VisitorTest.java
URL:
http://svn.apache.org/viewvc/wicket/branches/wicket-1.4.x/wicket/src/test/java/org/apache/wicket/VisitorTest.java?rev=926464&r1=926463&r2=926464&view=diff
==
---
wicket/branches/wicket-1.4.x/wicket/src/test/java/org/apache/wicket/VisitorTest.java
(original)
+++
wicket/branches/wicket-1.4.x/wicket/src/test/java/org/apache/wicket/VisitorTest.java
Tue Mar 23 05:23:58 2010
@@ -31,6 +31,7 @@ import org.apache.wicket.markup.html.for
* | +-E
* | +-F
* +-G
+ * +-H
*
*
* @author igor.vaynberg
@@ -52,7 +53,7 @@ public class VisitorTest extends WicketT
}
});
- Assert.assertEquals("BCDEFG", path.toString());
+ Assert.assertEquals("BCDEFGH", path.toString());
}
public void testContinuePostOrder()
@@ -69,10 +70,10 @@ public class VisitorTest extends WicketT
}
});
- Assert.assertEquals("BDFECGA", path.toString());
+ Assert.assertEquals("BDFECHGA", path.toString());
}
- public void testDoNotGoDeeper1()
+ public void testStop()
{
final StringBuilder path = new StringBuilder();
@@ -93,7 +94,7 @@ public class VisitorTest extends WicketT
Assert.assertEquals("RESULT", result);
}
- public void testStop()
+ public void testDoNotGoDeeper1()
{
final StringBuilder path = new StringBuilder();
@@ -110,7 +111,7 @@ public class VisitorTest extends WicketT
return CONTINUE_TRAVERSAL;
}
});
- Assert.assertEquals("BCG", path.toString());
+ Assert.assertEquals("BCGH", path.toString());
}
public void testDoNotGoDeeper2()
@@ -130,7 +131,7 @@ public class VisitorTest extends WicketT
return CONTINUE_TRAVERSAL;
}
});
- Assert.assertEquals("BCDEG", path.toString());
+ Assert.assertEquals("BCDEGH", path.toString());
}
@@ -145,12 +146,14 @@ public class VisitorTest extends WicketT
WebMarkupContainer e = new WebMarkupContainer("E");
WebMarkupContainer f = new WebMarkupContainer("F");
WebMarkupContainer g = new WebMarkupContainer("G");
+ WebMarkupContainer h = new WebMarkupContainer("H");
add(b);
add(c);
c.add(d);
c.add(e);
e.add(f);
add(g);
+ g.add(h);
}
}
[jira] Commented: (WICKET-2780) Containers in forms inside a border is not validated correctly
[
https://issues.apache.org/jira/browse/WICKET-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848371#action_12848371
]
Juergen Donnerstag commented on WICKET-2780:
I've tested against 1.4.7 and it works for me.
> Containers in forms inside a border is not validated correctly
> --
>
> Key: WICKET-2780
> URL: https://issues.apache.org/jira/browse/WICKET-2780
> Project: Wicket
> Issue Type: Bug
> Components: wicket
>Affects Versions: 1.4.1
> Environment: Tested with 1.4.1, but 1.4.7 code looks identical
>Reporter: Adriano dos Santos Fernandes
>Assignee: Juergen Donnerstag
> Attachments: bordervalidation.zip
>
>
> I've a border that have a form and in that form there is a DateField
> component. DateField is a FormComponentPanel with a embedded DateTextField.
> This code below in Form.java does not validate that component correctly, when
> an invalid date is entered.
> // Borders need special treatment
> if (!error[0] && (getParent() instanceof Border))
> {
> MarkupContainer border = getParent();
> Iterator iter = border.iterator();
> while (!error[0] && iter.hasNext())
> {
> Component child = iter.next();
> if ((child != this) && (child instanceof
> FormComponent))
> {
> visitor.component(child);
> }
> }
> }
> The problem is that the visitor is not used to go deeper in the hierarchy, so
> the DateTextField is never reached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-2780) Containers in forms inside a border is not validated correctly
[
https://issues.apache.org/jira/browse/WICKET-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848368#action_12848368
]
Juergen Donnerstag commented on WICKET-2780:
I've tested it against the latest 1.4 release (1.4.7) and it works for me.
> Containers in forms inside a border is not validated correctly
> --
>
> Key: WICKET-2780
> URL: https://issues.apache.org/jira/browse/WICKET-2780
> Project: Wicket
> Issue Type: Bug
> Components: wicket
>Affects Versions: 1.4.1
> Environment: Tested with 1.4.1, but 1.4.7 code looks identical
>Reporter: Adriano dos Santos Fernandes
>Assignee: Juergen Donnerstag
> Attachments: bordervalidation.zip
>
>
> I've a border that have a form and in that form there is a DateField
> component. DateField is a FormComponentPanel with a embedded DateTextField.
> This code below in Form.java does not validate that component correctly, when
> an invalid date is entered.
> // Borders need special treatment
> if (!error[0] && (getParent() instanceof Border))
> {
> MarkupContainer border = getParent();
> Iterator iter = border.iterator();
> while (!error[0] && iter.hasNext())
> {
> Component child = iter.next();
> if ((child != this) && (child instanceof
> FormComponent))
> {
> visitor.component(child);
> }
> }
> }
> The problem is that the visitor is not used to go deeper in the hierarchy, so
> the DateTextField is never reached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-2793) Incorrect decode parameters in AbstractRequestTargetUrlCodingStrategy#decodeParameters
[ https://issues.apache.org/jira/browse/WICKET-2793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848204#action_12848204 ] Igor Azarny commented on WICKET-2793: - The same mistake during url encode. See #appendValue line 113 > Incorrect decode parameters in > AbstractRequestTargetUrlCodingStrategy#decodeParameters > -- > > Key: WICKET-2793 > URL: https://issues.apache.org/jira/browse/WICKET-2793 > Project: Wicket > Issue Type: Bug > Components: wicket >Affects Versions: 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.4.6, 1.4.7 > Environment: Java 1.5, Tomcat 5.5 >Reporter: Igor Azarny > Original Estimate: 24h > Remaining Estimate: 24h > > In case of utf-8 url (see example below) created ValueMap in > AbstractRequestTargetUrlCodingStrategy#decodeParameters is incorrect. > Each key-value pair contains not decoded key and decoded value. > Proposed fix - line no 171 in > AbstractRequestTargetUrlCodingStrategy#decodeParameters > parameters.add(pairs[i], value); > shall be > parameters.add(urlDecodePathComponent(pairs[i]), value); > > Changes locally tested on 1.4.7 version - no failed test. But I am not sure > is AbstractRequestTargetUrlCodingStrategy covered by test cases. > And works correctly on tomcat. > URL in browser > http://jewelry.npa.com:8080/ws/shop/category/Браслеты/Колір_металу/Белый/Вставка/Бриллиант/Розмір/19.5/brand/Enigma/Проба/750/Матеріал/Золото/price/USD-31-60/Колір_вставки/Белый > URL in Tomcat > http://jewelry.npa.com:8080/ws/shop/category/%D0%91%D1%80%D0%B0%D1%81%D0%BB%D0%B5%D1%82%D1%8B/%D0%9A%D0%BE%D0%BB%D1%96%D1%80_%D0%BC%D0%B5%D1%82%D0%B0%D0%BB%D1%83/%D0%91%D0%B5%D0%BB%D1%8B%D0%B9/%D0%92%D1%81%D1%82%D0%B0%D0%B2%D0%BA%D0%B0/%D0%91%D1%80%D0%B8%D0%BB%D0%BB%D0%B8%D0%B0%D0%BD%D1%82/%D0%A0%D0%BE%D0%B7%D0%BC%D1%96%D1%80/19.5/brand/Enigma/%D0%9F%D1%80%D0%BE%D0%B1%D0%B0/750/%D0%9C%D0%B0%D1%82%D0%B5%D1%80%D1%96%D0%B0%D0%BB/%D0%97%D0%BE%D0%BB%D0%BE%D1%82%D0%BE/price/USD-31-60/%D0%9A%D0%BE%D0%BB%D1%96%D1%80_%D0%B2%D1%81%D1%82%D0%B0%D0%B2%D0%BA%D0%B8/%D0%91%D0%B5%D0%BB%D1%8B%D0%B9 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-2780) Containers in forms inside a border is not validated correctly
[
https://issues.apache.org/jira/browse/WICKET-2780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848191#action_12848191
]
Adriano dos Santos Fernandes commented on WICKET-2780:
--
Juergen:
public MyBorder(String id) {
super(id);
Form form = new Form("form");
form.add(getBodyContainer()); // ADDED
add(form);
Does not solve the test case problem nor my real case problem.
> Containers in forms inside a border is not validated correctly
> --
>
> Key: WICKET-2780
> URL: https://issues.apache.org/jira/browse/WICKET-2780
> Project: Wicket
> Issue Type: Bug
> Components: wicket
>Affects Versions: 1.4.1
> Environment: Tested with 1.4.1, but 1.4.7 code looks identical
>Reporter: Adriano dos Santos Fernandes
>Assignee: Juergen Donnerstag
> Attachments: bordervalidation.zip
>
>
> I've a border that have a form and in that form there is a DateField
> component. DateField is a FormComponentPanel with a embedded DateTextField.
> This code below in Form.java does not validate that component correctly, when
> an invalid date is entered.
> // Borders need special treatment
> if (!error[0] && (getParent() instanceof Border))
> {
> MarkupContainer border = getParent();
> Iterator iter = border.iterator();
> while (!error[0] && iter.hasNext())
> {
> Component child = iter.next();
> if ((child != this) && (child instanceof
> FormComponent))
> {
> visitor.component(child);
> }
> }
> }
> The problem is that the visitor is not used to go deeper in the hierarchy, so
> the DateTextField is never reached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
svn commit: r926153 - /wicket/branches/wicket-1.4.x/wicket/src/test/java/org/apache/wicket/VisitorTest.java
Author: ivaynberg
Date: Mon Mar 22 16:16:17 2010
New Revision: 926153
URL: http://svn.apache.org/viewvc?rev=926153&view=rev
Log:
visitor tests
Added:
wicket/branches/wicket-1.4.x/wicket/src/test/java/org/apache/wicket/VisitorTest.java
(with props)
Added:
wicket/branches/wicket-1.4.x/wicket/src/test/java/org/apache/wicket/VisitorTest.java
URL:
http://svn.apache.org/viewvc/wicket/branches/wicket-1.4.x/wicket/src/test/java/org/apache/wicket/VisitorTest.java?rev=926153&view=auto
==
---
wicket/branches/wicket-1.4.x/wicket/src/test/java/org/apache/wicket/VisitorTest.java
(added)
+++
wicket/branches/wicket-1.4.x/wicket/src/test/java/org/apache/wicket/VisitorTest.java
Mon Mar 22 16:16:17 2010
@@ -0,0 +1,157 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.wicket;
+
+import junit.framework.Assert;
+
+import org.apache.wicket.Component.IVisitor;
+import org.apache.wicket.markup.html.WebMarkupContainer;
+import org.apache.wicket.markup.html.form.FormComponent;
+
+/**
+ *
+ * A
+ * +-B
+ * +-C
+ * | +-D
+ * | +-E
+ * | +-F
+ * +-G
+ *
+ *
+ * @author igor.vaynberg
+ */
+public class VisitorTest extends WicketTestCase
+{
+
+ public void testContinueTraversal()
+ {
+ final StringBuilder path = new StringBuilder();
+
+ TestContainer container = new TestContainer();
+ container.visitChildren(new IVisitor()
+ {
+ public Object component(Component component)
+ {
+ path.append(component.getId());
+ return CONTINUE_TRAVERSAL;
+ }
+ });
+
+ Assert.assertEquals("BCDEFG", path.toString());
+ }
+
+ public void testContinuePostOrder()
+ {
+ final StringBuilder path = new StringBuilder();
+
+ TestContainer container = new TestContainer();
+ FormComponent.visitComponentsPostOrder(container, new
IVisitor()
+ {
+ public Object component(Component component)
+ {
+ path.append(component.getId());
+ return CONTINUE_TRAVERSAL;
+ }
+ });
+
+ Assert.assertEquals("BDFECGA", path.toString());
+ }
+
+ public void testDoNotGoDeeper1()
+ {
+ final StringBuilder path = new StringBuilder();
+
+ TestContainer container = new TestContainer();
+ Object result = container.visitChildren(new
IVisitor()
+ {
+ public Object component(Component component)
+ {
+ path.append(component.getId());
+ if ("D".equals(component.getId()))
+ {
+ return "RESULT";
+ }
+ return CONTINUE_TRAVERSAL;
+ }
+ });
+ Assert.assertEquals("BCD", path.toString());
+ Assert.assertEquals("RESULT", result);
+ }
+
+ public void testStop()
+ {
+ final StringBuilder path = new StringBuilder();
+
+ TestContainer container = new TestContainer();
+ container.visitChildren(new IVisitor()
+ {
+ public Object component(Component component)
+ {
+ path.append(component.getId());
+ if ("C".equals(component.getId()))
+ {
+ return
CONTINUE_TRAVERSAL_BUT_DONT_GO_DEEPER;
+ }
+ return CONTINUE_TRAVERSAL;
+ }
+ });
+ Assert.assertEquals("BCG", path.toString());
+ }
+
+ public void testDoNotGoDeeper2()
+ {
+ final StringBuilder path = new St
[jira] Updated: (WICKET-2794) Not all exceptions are properly handled by the WicketFilter -> results in empty response document with unset status code -> seen as HTTP_OK by client
[ https://issues.apache.org/jira/browse/WICKET-2794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Oldiges updated WICKET-2794: -- Attachment: wicket2794.zip quickstart > Not all exceptions are properly handled by the WicketFilter -> results in > empty response document with unset status code -> seen as HTTP_OK by client > - > > Key: WICKET-2794 > URL: https://issues.apache.org/jira/browse/WICKET-2794 > Project: Wicket > Issue Type: Bug > Components: wicket >Affects Versions: 1.4.7 >Reporter: Christian Oldiges >Priority: Minor > Attachments: wicket2794.zip > > > Our custom ResourceStreamLocator might throw RuntimeExceptions. > When doing so, the exception handling of the WicketFilter doesnt properly > handle this situation and creates an empty document with unset response code, > which is usually sent to the client as HTTP_OK. > quickstart follows. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (WICKET-2794) Not all exceptions are properly handled by the WicketFilter -> results in empty response document with unset status code -> seen as HTTP_OK by client
Not all exceptions are properly handled by the WicketFilter -> results in empty response document with unset status code -> seen as HTTP_OK by client - Key: WICKET-2794 URL: https://issues.apache.org/jira/browse/WICKET-2794 Project: Wicket Issue Type: Bug Components: wicket Affects Versions: 1.4.7 Reporter: Christian Oldiges Priority: Minor Our custom ResourceStreamLocator might throw RuntimeExceptions. When doing so, the exception handling of the WicketFilter doesnt properly handle this situation and creates an empty document with unset response code, which is usually sent to the client as HTTP_OK. quickstart follows. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (WICKET-2793) Incorrect decode parameters in AbstractRequestTargetUrlCodingStrategy#decodeParameters
Incorrect decode parameters in AbstractRequestTargetUrlCodingStrategy#decodeParameters -- Key: WICKET-2793 URL: https://issues.apache.org/jira/browse/WICKET-2793 Project: Wicket Issue Type: Bug Components: wicket Affects Versions: 1.4.7, 1.4.6, 1.4.5, 1.4.4, 1.4.3, 1.4.2 Environment: Java 1.5, Tomcat 5.5 Reporter: Igor Azarny In case of utf-8 url (see example below) created ValueMap in AbstractRequestTargetUrlCodingStrategy#decodeParameters is incorrect. Each key-value pair contains not decoded key and decoded value. Proposed fix - line no 171 in AbstractRequestTargetUrlCodingStrategy#decodeParameters parameters.add(pairs[i], value); shall be parameters.add(urlDecodePathComponent(pairs[i]), value); Changes locally tested on 1.4.7 version - no failed test. But I am not sure is AbstractRequestTargetUrlCodingStrategy covered by test cases. And works correctly on tomcat. URL in browser http://jewelry.npa.com:8080/ws/shop/category/Браслеты/Колір_металу/Белый/Вставка/Бриллиант/Розмір/19.5/brand/Enigma/Проба/750/Матеріал/Золото/price/USD-31-60/Колір_вставки/Белый URL in Tomcat http://jewelry.npa.com:8080/ws/shop/category/%D0%91%D1%80%D0%B0%D1%81%D0%BB%D0%B5%D1%82%D1%8B/%D0%9A%D0%BE%D0%BB%D1%96%D1%80_%D0%BC%D0%B5%D1%82%D0%B0%D0%BB%D1%83/%D0%91%D0%B5%D0%BB%D1%8B%D0%B9/%D0%92%D1%81%D1%82%D0%B0%D0%B2%D0%BA%D0%B0/%D0%91%D1%80%D0%B8%D0%BB%D0%BB%D0%B8%D0%B0%D0%BD%D1%82/%D0%A0%D0%BE%D0%B7%D0%BC%D1%96%D1%80/19.5/brand/Enigma/%D0%9F%D1%80%D0%BE%D0%B1%D0%B0/750/%D0%9C%D0%B0%D1%82%D0%B5%D1%80%D1%96%D0%B0%D0%BB/%D0%97%D0%BE%D0%BB%D0%BE%D1%82%D0%BE/price/USD-31-60/%D0%9A%D0%BE%D0%BB%D1%96%D1%80_%D0%B2%D1%81%D1%82%D0%B0%D0%B2%D0%BA%D0%B8/%D0%91%D0%B5%D0%BB%D1%8B%D0%B9 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-2792) Wicket.replaceOuterHtml and jQuery dragdrop on IE
[ https://issues.apache.org/jira/browse/WICKET-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernesto Reinaldo Barreiro updated WICKET-2792: -- Labels: Wicket AJAX jQuery drag and drop (was: ) Description: 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! Ernesto was: First of all I want to state that I´m not 100% sure this Wicket problem but the only way I have found to reproduce it is using static HTML is by means of 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! Ernesto Environment: WINDOWS, Internet Explorer (was: WINDOW, Internet Explorer) > Wicket.replaceOuterHtml and jQuery dragdrop on IE > - > > Key: WICKET-2792 > URL: https://issues.apache.org/jira/browse/WICKET-2792 > Project: Wicket > Issue Type: Bug >Affects Versions: 1.4.7 > Environment: WINDOWS, Internet Explorer >Reporter: Ernesto Reinaldo Barreiro > > 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 w
[jira] Created: (WICKET-2792) Wicket.replaceOuterHtml and jQuery dragdrop on IE
Wicket.replaceOuterHtml and jQuery dragdrop on IE - Key: WICKET-2792 URL: https://issues.apache.org/jira/browse/WICKET-2792 Project: Wicket Issue Type: Bug Affects Versions: 1.4.7 Environment: WINDOW, Internet Explorer Reporter: Ernesto Reinaldo Barreiro First of all I want to state that I´m not 100% sure this Wicket problem but the only way I have found to reproduce it is using static HTML is by means of 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! Ernesto -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
