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

Sven Meier commented on WICKET-4620:
------------------------------------

>You mention there not being a 5th row. Are you perhaps referring to the fact 
>that
>Wicket doesn't usually populate the tables before processing a form post?

Yes, more correctly: Wicket populates repeaters for rendering only. They stay 
in the session (if not stateless) so they can receive callback via Ajax or 
standard requests.

>  my StatelessDataTable class ... preparing the table ... before the form gets 
> processed
> (currently in onInitialize()).

Aha, that's not how we do things normally in Wicket.

> that was quite hard to figure out.

Should give you a hint that it's not the 'usual' way ;).

Wicket doesn't have a 'rewind' step as Tapestry has. If the component isn't in 
the session there's no way to trigger it with a request.
If you want to keep your table (and its containing page) stateless, you should 
use Bookmarkable links with page parameters.
                
> 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

        

Reply via email to