[
https://issues.apache.org/jira/browse/WICKET-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12804041#action_12804041
]
Igor Vaynberg commented on WICKET-2684:
---------------------------------------
404 may be acceptable in your particular app, but users of my backend would be
highly perplexed if all of a sudden they saw a generic 404 when clicking an
edit link.
if you use stateless pages and stateless links to do this sort of thing then
you know the risks.
> After all, it's not wicket business what ids i assign to my components
it is ListViews, and all other components that do this, job to assign the ids
and make sure they are unique. the fact that these ids even exist is an
internal implementation detail.
> (and actually nothing in wicket depends on them being numeric).
not true. maybe not in 1.5 with Juergen's changes, but in 1.4 afair there are
places that check that id is purely numeric and if it is it is assumed to be
assigned to a wicket-created component representing an item inside a repeater.
once again an implementation detail.
you want more control? you have two options: use a bookmarkable link or use a
low-level repeater where you have total control - RepeatingView
> 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.
