On Sun, 2005-09-11 at 10:16 +1000, Brett Porter wrote: > Can you explain the reason for going with a property attribute and using > methods that don't match the field name? This means that they don't work > under bean conventions (and IDE generation of getters/setters :)
Probably should have just pulled from my stock pile of quotes: "... this is the Uniform Access principle. Hiding the difference between access to instance variables and calculated values shields users from the implementation of your class ..." -- Object Software Construction, Bertrand Meyer Which is really what a property is. Even in the simplest example you google for shows that even a simple field may not match up name wise and it doesn't matter as tools will use the bean tools which look for methods. http://www.oreilly.com/catalog/javabeans/chapter/ch01.html -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
