[
https://issues.apache.org/jira/browse/WICKET-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908516#action_12908516
]
Pedro Santos commented on WICKET-1177:
--------------------------------------
I didn't understand
Imaging for instance if we have:
<table wicket:id="container">
<tbody>
<tr wicket:id="repeater">(...)</tr>
</tbody>
</table>
How an out of box solution would know that the new repeater item should be
placed at the tbody, instead at the table?
Shouldn't this child parent resolution be implemented case by case?
> partial ajax updates on repeater components
> -------------------------------------------
>
> Key: WICKET-1177
> URL: https://issues.apache.org/jira/browse/WICKET-1177
> Project: Wicket
> Issue Type: Wish
> Components: wicket
> Affects Versions: 1.3.0-rc2
> Reporter: Peter Ertl
> Assignee: Matej Knopp
> Fix For: 1.5-M3
>
>
> I try to explain the problem using an example:
> Imagine having a guestbook page where you can add new user entries via ajax
> post...
> Assume we are using RefreshingView to display the user entries. Once a user
> submits a new post the view should not be re-rendered in the ajax response
> completely but only the new user entry.
> Technically it's easy to address the view items by using e.g.
> ListItem#setOutputMarkupId(true).
> However, things are more complicated.
> When the user clicks on the submit button a background ajax request is
> created and a form submit listener is invoked. There the new guestbook post
> is saved in the data model. Then you want to update the list with the new
> entry using target.addComponent(..) . Also, applying a yellow fade effect to
> the component would be cool as an visual indication for the user. However,
> there is no way I can think of to get the proper view item(s) for the model
> object (=new user entry).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
