[
https://issues.apache.org/jira/browse/WICKET-4620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400273#comment-13400273
]
Trejkaz commented on WICKET-4620:
---------------------------------
With the way the code is now, if the user checks the check box on the 5th row,
Wicket will process them as having checked the check box on the 5th row. If new
rows appear in the meantime, the action will be applied to the wrong item.
If the IDs were based on the model objects, an action on model ID 7 will be
applied to model ID 7 regardless of what other model objects are in the table
when the form is eventually processed.
> Ability to choose the child ID for repeating views and the row ID for
> DataTable
> -------------------------------------------------------------------------------
>
> Key: WICKET-4620
> URL: https://issues.apache.org/jira/browse/WICKET-4620
> Project: Wicket
> Issue Type: New Feature
> Components: wicket
> Reporter: Trejkaz
>
> We are extensively using stateless behaviour in our application.
> Because our pages are stateless, we can't rely on the IDs for rows being the
> same between two visits to the same page - something might have happened to
> shift the rows up or down such as another user inserting or removing rows.
> Because of this, I would like to use the ID of our actual model objects as
> the child ID, but there are two barriers to achieving this:
> 1. Even though newChildId() in RepeatingView is public, it isn't passed the
> model object so I can't derive the ID from the model object.
> 2. Even though I could extend DataGridView, I can't customise my DataTable
> subclass to return the subclass because it's being constructed in the
> constructor.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
