[jira] [Comment Edited] (WICKET-4630) StatelessDataTable (like DefaultDataTable but for use in stateless pages)

["Trejkaz (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-4630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937764#comment-13937764 ] 

Trejkaz edited comment on WICKET-4630 at 3/17/14 1:03 PM:
----------------------------------------------------------

Is there some way to make a stateless alternative to DataTable then?

All I really want is a way to specify the ID for rows of repeatable things, so that when the POST comes in later, we can apply edits to what they were requested for.

With the current Wicket, this is impossible, because the IDs of the table change each time you refresh the page, for stateless pages.

For stateful pages, there is no problem in this regard since the entire table is still in memory when the POST is processed, but there are other usability problems with users hitting Reload and not seeing the data refresh (due to these issues, we have decided to enforce that all pages be stateless.)

If I'm misunderstanding how all this is supposed to work, then an example of how to do it right would be good. Last time, someone basically said I was doing it wrong without offering any better alternative.


was (Author: trejkaz):
Is there some way to make a stateless alternative to DataTable then?

All I really want is a way to specify the ID for rows of repeatable things, so that when the POST comes in later, we can apply edits to what they were requested for.

With the current Wicket, this is impossible, because the IDs of the table change each time you refresh the page, for stateless pages.

For stateful pages, there is no problem in this regard since the entire table is still in memory when the POST is processed, but there are other usability problems with users hitting Reload and not seeing the data refresh (due to these issues, we have decided to enforce that all pages be stateless.)


> StatelessDataTable (like DefaultDataTable but for use in stateless pages)
> -------------------------------------------------------------------------
>
>                 Key: WICKET-4630
>                 URL: https://issues.apache.org/jira/browse/WICKET-4630
>             Project: Wicket
>          Issue Type: New Feature
>            Reporter: Trejkaz
>
> (inspired by WICKET-4620)
> We have a StatelessDataTable which is implemented like DefaultDataTable but replacing all links with bookmarkable links.
> Problem is, when there are form fields inside the table, the form doesn't process any of the fields in the table unless you perform a workaround which is apparently the "wrong" way to do it:
>     @Override
>     protected void onInitialize() {
>         super.onInitialize();
>         beforeRender();
>     }
> If there is a "right" way to do it, I think this warrants a stateless table component in Wicket so that people don't implement it from scratch the "wrong" way, which seems to be the only option at present.



--
This message was sent by Atlassian JIRA
(v6.2#6252)