[
https://issues.apache.org/jira/browse/WICKET-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg resolved WICKET-2684.
-----------------------------------
Resolution: Invalid
yes, you can. and it is. look at my explanation. the index is translated into
the model which is in turn translated into the PK. how do you think thousands
of other people use wicket with databases without messing with repeater ids? or
do all wicket apps out there suffer from concurrency issues where pressing a
delete button deletes the wrong thing?
> 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.
