Considering that having more than one constructor seems to scare out noobs (take a look at DDC for a prime example), having them, when they are not necessary, is not good for the API.
The constructor of a component is the first thing any one sees when using it (apart from the LongAndVerboseClassNameOfTheComponent), so not having the parameter there makes the learning curve less. Martijn On 7/10/07, Matej Knopp <[EMAIL PROTECTED]> wrote:
Sorry for not voting in this reply, but do you really consider the constructor with type parameter confusing for noobs? -Matej On 7/10/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > Matej had the brilliant idea of auto discovery of the type parameter > for FormComponents when they use a PropertyModel or > CompoundPropertyModel. In order to remove confusion for noobs, and to > point out that there is a Better Way (tm) I propose the following > options: > > For those wondering if it is still possible to set the target type: > yes you can, just use the setType() method on the form component. > > I know it is a tad late in the game, but I think the clean up is > something worthwile. > > [ ] remove the affected FormComponent constructors with the type parameter > [ ] deprecate the affected FormComponent constructors with the type parameter > [ ] leave them > > Martijn > > -- > Wicket joins the Apache Software Foundation as Apache Wicket > Apache Wicket 1.3.0-beta2 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta2/ >
-- Wicket joins the Apache Software Foundation as Apache Wicket Apache Wicket 1.3.0-beta2 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta2/
