Igor Vaynberg wrote: > On 7/7/07, *Eelco Hillenius* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > > two points: > > > > this is relatively new, i think it made it in just before > 1.3-beta1 or > > somewhere there > > I think it's been in there for quite a while. But as I never depended > on it, I wouldn't know. > > > you didnt know about it, so of course you would be writing > > getters/setters > > Heh. My point is that everyone did that on this project, including you > as far as I can see. > > > i havent done any real wicket coding on that for a while though. i have > been in the j2me land since this was introduced. on my other projects i > use this feature all the time and dont imagine coding wicket without it > anymore :)
I'm with Igor on this. The common use-case is indeed for accessing private fields of your Page or whatever. With this feature, much boilerplate code is removed. We should not make this hard. Please don't remove this. -1 Of course, if Java had compile-time MyClass#field syntax, then that could enforce the visibility and everyone would be happy. Regards, Al -- Alastair Maw Wicket-biased blog at http://herebebeasties.com ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
