[
https://issues.apache.org/jira/browse/WICKET-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803660#action_12803660
]
Marat Radchenko commented on WICKET-2684:
-----------------------------------------
> how is that fragile?
>From issue description: Relying on index is fragile because users can be
>added/deleted by other requests.
I can't guarantee that link with particular index will refer to same user when
page is initially rendered and when it is submitted.
> 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.
