Just wondering if it would be possible and if so, worthwhile, to have
a 'validation' point somewhere in the (development) page processing,
to try & warn about things that are valid but probably not what's
intended.

  The specific issue that springs to mind is that raised in
WICKET-1163, i.e. where you have a component that's had both
setVisible(false) and setOutputMarkupId(true) called on it, but not
setOutputMarkupPlaceholderTag(true).  It seems to me that that it
might be worth a warning in the log file when in development mode, at
least, and there might be other combinations that might be worth
detecting.

Comments?

/Gwyn
-- 
Download Wicket 1.3.0-rc1 now! - http://wicketframework.org

Reply via email to