[jira] Commented: (WICKET-2684) Provide a way to disable "Child component has a non-safe child id"

["Juergen Donnerstag (JIRA)" <ji...@apache.org>]

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

Juergen Donnerstag commented on WICKET-2684:
--------------------------------------------

In 1.5 any restriction on child component ids has been removed, except they have to be unique for the container. That was possible because of the changes to the render process.

I need to look into 1.4 to evaluate the options

> 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
>
> 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.