On Thu, 05 Feb 2009, Daniel Ferreira Castro wrote: > I think, in my opinion, that the approach of declaring the Form as an inner > class makes the code more "dirty". I mean, the Page class grows a lot and > by inspecting the code is hard to understand at a first glance the scope of > each entity and field. So I prefer to declare the Form as a top class > instead inner class.
As a rule of a thumb, it's a good idea to thrive to follow the single responsibility principle [1] also with Wicket classes. This might or might not get more complicated with inter-component dependencies. [1] http://www.objectmentor.com/resources/articles/srp.pdf Best wishes, Timo --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
