Comments on: Repainting only newly-created repeater items via ajax http://wicketinaction.com/2008/10/repainting-only-newly-created-repeater-items-via-ajax/ A comprehensive guide for Java developers building Wicket-based web applications Tue, 22 Nov 2011 11:29:42 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: ivaynberg http://wicketinaction.com/2008/10/repainting-only-newly-created-repeater-items-via-ajax/comment-page-1/#comment-1104 ivaynberg Mon, 22 Aug 2011 22:50:11 +0000 http://wicketinaction.com/?p=252#comment-1104 this is not a "weakness" of Wicket in particular. all frameworks would suffer this particular problem. Eg how would spring-mvc know where to put the new row in markup and what tag should represent the new row, youd have to hand-code it just like you would in wicket? maybe the repeater uses different tags based on some business logic to represent each row... only the user of the repeater knows how to handle this situation. i suppose its possible to integrate this usecase better into wicket, maybe something for a later version, feel free to open an RFE in our jira. this is not a “weakness” of Wicket in particular. all frameworks would suffer this particular problem. Eg how would spring-mvc know where to put the new row in markup and what tag should represent the new row, youd have to hand-code it just like you would in wicket? maybe the repeater uses different tags based on some business logic to represent each row… only the user of the repeater knows how to handle this situation. i suppose its possible to integrate this usecase better into wicket, maybe something for a later version, feel free to open an RFE in our jira.

]]> By: paul http://wicketinaction.com/2008/10/repainting-only-newly-created-repeater-items-via-ajax/comment-page-1/#comment-1103 paul Mon, 22 Aug 2011 18:39:05 +0000 http://wicketinaction.com/?p=252#comment-1103 Thank you for this write-up, it was just what I was looking for. I believe this is a clear indication of the fundamental weakness of Wicket, or more generally, most server-centric frameworks. After gaining proficiency in Wicket, and then engaging in black magic such as this, would the programmer have really saved time compared with using even the most basic frameworks (e.g. javascript + spring-mvc)? What about a more powerful framework, such as GWT? Going further, would the project be more maintainable? I personally believe that the answer to these questions is "no". In the case of Wicket we've added another complicated layer of abstraction (loss of maintainability), and in return we've lost performance (many unnecessary hooks from client to server; unnecessary storage of client-side state on server, etc). Thank you for this write-up, it was just what I was looking for. I believe this is a clear indication of the fundamental weakness of Wicket, or more generally, most server-centric frameworks.

After gaining proficiency in Wicket, and then engaging in black magic such as this, would the programmer have really saved time compared with using even the most basic frameworks (e.g. javascript + spring-mvc)? What about a more powerful framework, such as GWT? Going further, would the project be more maintainable?

I personally believe that the answer to these questions is “no”. In the case of Wicket we’ve added another complicated layer of abstraction (loss of maintainability), and in return we’ve lost performance (many unnecessary hooks from client to server; unnecessary storage of client-side state on server, etc).

]]> By: ivaynberg http://wicketinaction.com/2008/10/repainting-only-newly-created-repeater-items-via-ajax/comment-page-1/#comment-809 ivaynberg Wed, 09 Mar 2011 16:03:09 +0000 http://wicketinaction.com/?p=252#comment-809 @Daniel, you are more then welcome to post a non-working quickstart to wicket's mailing lists. Not much, ajax-wise, has changed between 1.4 and 1.5 so it should still work. @Daniel, you are more then welcome to post a non-working quickstart to wicket’s mailing lists. Not much, ajax-wise, has changed between 1.4 and 1.5 so it should still work.

]]> By: Daniel http://wicketinaction.com/2008/10/repainting-only-newly-created-repeater-items-via-ajax/comment-page-1/#comment-779 Daniel Tue, 08 Feb 2011 22:58:39 +0000 http://wicketinaction.com/?p=252#comment-779 Hi Igor! Great tutorial on a very handy feature. I tried your sample project and it works as expected. When I tried it in my own project however, I couldn't get it to work. I keep getting 'unable to find markup for the component' errors. I cannot figure it out, do you have any idea without going through the code? The JavaScript that adds the new tag works fine but it doesn't seem to be found by on the server side. I know this post is a bit old, have you added and support for this in 1.5? Thanks Hi Igor!

Great tutorial on a very handy feature.
I tried your sample project and it works as expected.
When I tried it in my own project however, I couldn’t get it to work. I keep getting ‘unable to find markup for the component’ errors. I cannot figure it out, do you have any idea without going through the code? The JavaScript that adds the new tag works fine but it doesn’t seem to be found by on the server side.

I know this post is a bit old, have you added and support for this in 1.5?

Thanks

]]> By: ivaynberg http://wicketinaction.com/2008/10/repainting-only-newly-created-repeater-items-via-ajax/comment-page-1/#comment-562 ivaynberg Thu, 30 Jul 2009 17:02:03 +0000 http://wicketinaction.com/?p=252#comment-562 @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. @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 http://wicketinaction.com/2008/10/repainting-only-newly-created-repeater-items-via-ajax/comment-page-1/#comment-557 monika Tue, 28 Jul 2009 09:45:01 +0000 http://wicketinaction.com/?p=252#comment-557 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 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 http://wicketinaction.com/2008/10/repainting-only-newly-created-repeater-items-via-ajax/comment-page-1/#comment-542 sven Tue, 30 Jun 2009 15:11:36 +0000 http://wicketinaction.com/?p=252#comment-542 For record - maybe I found solution - add them into collection and use fragments for the two different styles of rows. For record – maybe I found solution – add them into collection and use fragments for the two different styles of rows.

]]> By: sven http://wicketinaction.com/2008/10/repainting-only-newly-created-repeater-items-via-ajax/comment-page-1/#comment-541 sven Tue, 30 Jun 2009 14:17:56 +0000 http://wicketinaction.com/?p=252#comment-541 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. 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 http://wicketinaction.com/2008/10/repainting-only-newly-created-repeater-items-via-ajax/comment-page-1/#comment-540 sven Tue, 30 Jun 2009 14:15:41 +0000 http://wicketinaction.com/?p=252#comment-540 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 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 http://wicketinaction.com/2008/10/repainting-only-newly-created-repeater-items-via-ajax/comment-page-1/#comment-539 sven Tue, 30 Jun 2009 13:13:44 +0000 http://wicketinaction.com/?p=252#comment-539 Very nice. But how to get markupId for the remove operation? Very nice. But how to get markupId for the remove operation?

]]>