Our HTML monkey got me to make the ids of a RepeatingView valid (ie not just
a number) but I
think we got caught by this (from org.apache.wicket.markup.Markup):
// TODO Post 1.2: A component path e.g. "panel:label" does not
match 1:1
// with the markup in case of ListView, where the path contains
a number
// for each list item. E.g. list:0:label. What we currently do
is simply
// remove the number from the path and hope that no user uses
an integer
// for a component id. This is a hack only. A much better
solution would
// delegate to the various components recursivly to search
within there
// realm only for the components markup. ListItems could then
simply
// do nothing and delegate to their parents.
Maybe a logger warning or assert if the developer tries to use an id that is
not \d+ and fix the comment in RepeatingView that says newChildId starts
with "id"?
Cheers
Sam
--
View this message in context:
http://www.nabble.com/RepeatingView-id-tf4427681.html#a12630767
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
