[
https://issues.apache.org/jira/browse/WICKET-4620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400961#comment-13400961
]
Trejkaz commented on WICKET-4620:
---------------------------------
That's what we're doing for all links already.
So what is the "right" way to do a table full of form fields statelessly?
If there is a "right" way to do stateless things in Wicket, it would be nice to
have a StatelessDataTable and so forth in the core so that we don't have to
reimplement it from scratch [incorrectly] every time.
> 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
