You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2014/03/18 13:00:48 UTC
[jira] [Reopened] (WICKET-4630) StatelessDataTable (like
DefaultDataTable but for use in stateless pages)
[ https://issues.apache.org/jira/browse/WICKET-4630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov reopened WICKET-4630:
-------------------------------------
> 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
> Attachments: brokenstatelesstables.zip
>
>
> (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)