When instantiating a RepeatingView, is there a case where RepeatingView(String id, IModel model) would be used instead of RepeatingView(String id) ? It seems that RepeatingView's (and RefreshingView's) "model" is unused. If this is the case, to help users (as opposed to sub-classers who may conceivably come up with a use for the model) of RepeatingView should the constructor "RepeatingView(String id, IModel model)" be declared protected rather than public to avoid confusion? (If this is a valid argument, does the same apply all the way up to MarkupContainer?) It would be nice _if it were possible_ to even throw some sort of RuntimeException (UnsupportedOperationException?) in RepeatingView's setModel method (that sub-classers would need to override to behave in the usual manner (see MarkupContainer) if the model is somehow relevant for their sub-class - but of course, this would be, at best, tricky as they would not be able to call super.setModel and would have to provide their own implementation ;-) .
Regards - Cemal http://jWeekend.co.uk http://jWeekend.co.uk -- View this message in context: http://www.nabble.com/RepeatingView-constructors-tf4830379.html#a13819597 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
