Hi,
the problem is when can you call that method?
Because currently you have to render it once because before that
the component has no idea of its markup and because of that no idea
of its id.
why should a component not provide information about the id it will
render later in its markup? If the generation of the id is separated
from the rendering (which it is through the getMarkupId() call which
would probably map to the path of the component and be used by the
rendering code as well) I don't see a problem with that...
Maybe it could make sense to make this even default for components,
because it's a basic requirement for ajax and javascript behaviour of
components. Having id's for component by default in the markup
wouldn't cost so much. This way a default implementation for the
getMarkupId() call could be provided. If implemented as interface,
every component would have to implement this on its own (which could
generate confusion and make it impossible to have a pluggable
strategy class for id generation)
Regards,
Ralf
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
