<igor.vaynberg <at> gmail.com> writes: > the reason why we use getters and setters and not public fields is > because we never know what is going to happen later - and because it > is hard to refactor public field access into a getter or a setter we > opt for the more flexible, but more verbous way first. > > with property model this argument does not exist. it first tries to > look for a getter/setter and if not found defaults to the field > itself. so a refactoring there - if you are only concerned with > property models, is to simply put a getter/setter in place.
This is a good point. The only concern left is the use of SecurityManager that doesn't grant the app the ReflectPermission (probably in a hosting environment). I think this is a tradeoff that is up to the app developers to decide (as long as they're informed of this). ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
