On Mar 23, 2008, at 5:45 PM, Gustavo Pizano wrote:
I hadn't think about hwat you said, but you definelty right, I can
get rid o the getters and setters off, I will only need a Person
attribute,
When surprises occur, I have found that I need to be able to debug
when an attribute's value is being set or gotten. Without getters and
setters, one cannot set a Java debugger breakpoint to pause when an
attribute's value is being set or gotten. This is a restriction that
isn't acceptable to me.
I also don't like public instance variables because they expose an
object's implementation which violates a principle of object-oriented
design. Sure, you can say that you'll never access a public attribute
from outside the object's scope, but the temptation is there when the
instance variable is public.
But regardless of which you choose, your WO app will work correctly.
Aloha,
Art
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
