Comments on: Repainting only newly-created repeater items via ajax

By: ivaynberg

ivaynberg — Thu, 30 Jul 2009 17:02:03 +0000

@monika: Based on your table it can be quiet a lot of data. Also based on complexity of the data – you might not want to run the server side code/queries necessary to rebuild that data. Anyways, the point of this article was to demonstrate a partial update to the table, not a partial update to the page which is trivial in Wicket.

By: monika

monika — Tue, 28 Jul 2009 09:45:01 +0000

A nice tutorial, thanks. However if you want less Javascript magic and more Wicket, then I don’t think you should be doing such a trick to save a few hundred bytes of bandwidth. This blog entry provides a solution for this case:
http://oktech.hu/blog/2009/07/adding-and-removing-rows-in-wicket.html

By: sven

sven — Tue, 30 Jun 2009 15:11:36 +0000

For record – maybe I found solution – add them into collection and use fragments for the two different styles of rows.

By: sven

sven — Tue, 30 Jun 2009 14:17:56 +0000

Note – they cannot be added into the collection of contacts (which works nicely), because they act as subrows – they are little different then the main rows.

By: sven

sven — Tue, 30 Jun 2009 14:15:41 +0000

Hi again, I’m having big problems with refresh.
After adding the rows to dataView (refreshingView in your case), they are displayed correctly. But after F5 (refresh), they disappear.
I added ‘expanded’ property to model item. And when populating the item (populateItem), I check it. If it is set, I create the new rows with your buildItem method. But as the result, the rows are displayed above the current row, which is logical, but wrong.
How can the rows be displayed under the current row (with which I work in populateItem method), please?
Thanks a lot

By: sven

sven — Tue, 30 Jun 2009 13:13:44 +0000

Very nice. But how to get markupId for the remove operation?

By: Matt Shannon

Matt Shannon — Fri, 08 May 2009 06:33:07 +0000

Nice example, note there is a bug I believe. onSubmit of form, you should create a new contact object and associate it with your form model. Otherwise, you will continue to re-use the same single contact instance that was supplied on form creation.

I created an ajaxlink to remove that seems to work …

add(new AjaxLink(“remove”)
{
public void onClick(AjaxRequestTarget target)
{
String markupId = …

target.prependJavascript(“var item=document.getElementById(‘”
+ markupId + “‘);Wicket.$(‘” + container.getMarkupId()
+ “‘).removeChild(item);”);

contacts.remove(…);
repeater.remove(…);
}
});

By: glenn

glenn — Sun, 16 Nov 2008 12:00:39 +0000

I found this link as helpfulon this. I think I see what i need..
http://donteattoomuch.blogspot.com/2008/04/partial-ajax-update-capable-list-view.html

By: ivaynberg

ivaynberg — Fri, 07 Nov 2008 22:30:17 +0000

@Jeff: It should be possible albeit a little harder. You will have to iterate over all existing items, see which ones have been removed and added and spit out javascript to synchronize server with client. Component#hasBeenRendered() can come in handy when figuring out which items have been left over from the previous request.

By: Jeff

Jeff — Fri, 07 Nov 2008 21:54:36 +0000

Great example! Could this be done with a RefreshingView and an AjaxLink?