[
https://issues.apache.org/jira/browse/WICKET-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12804035#action_12804035
]
Marat Radchenko commented on WICKET-2684:
-----------------------------------------
> the index is translated into the model which is in turn translated into the PK
Translate 1-3 numbers into "ann", "john", "peter", please.
Also, don't forget that after you initially loaded a stateless page with user
list (but before you clicked on a link inside repeater), "bob" registered.
> or do all wicket apps out there suffer from concurrency issues where pressing
> a delete button deletes the wrong thing?
All that do not use persistent object primary key as repeater child id.
> Provide a way to disable "Child component has a non-safe child id"
> -------------------------------------------------------------------
>
> Key: WICKET-2684
> URL: https://issues.apache.org/jira/browse/WICKET-2684
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.4.5
> Reporter: Marat Radchenko
> Assignee: Igor Vaynberg
>
> AbstractRepeater.onBeforeRender checks child component ids to be digit-only.
> While i (kinda) understand reasoning behind this behavior, it is sometimes
> not what i want.
> One of examples is user list with login acting as primary key on a stateless
> page. Relying on index is fragile because users can be added/deleted by other
> requests, so i want to use user login as repeater child ids, however it
> triggers warning.
> That check should be either disableable globally or on per-component basis
> (latter is more desired), so I can tell AbstractRepeater that i know what i'm
> doing and deliberately want non-numeric ids.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
