I just read the article and some of the posts. I am kind of new in Java programming, but the thing is this article made an impact on me. first, the title sure maske you want to read it.
When I was in college, I remember my first programming teacher once said that the attributes of an object are private and that you provide public methods to access or modify those attributes. Then when I started working, while still in college, I remeber my boss told me to use Javabeans to provide this behavior. So for me, Java beans are basically get/set methods. Maybe its right what was mentioned in the article that it is the simple or easy way to go. I started reading an article about javabeans and then a coworker came to me and said: "just get and set mehotds". So pretty much that was the idea I had in mind.
Now working, I find people here create Javabeans arguing to be following the Valueobject pattern, but they create many of them.
Anyway I just wanted to say, that maybe we have a bad conception of javabeans or OO itself. I found the article very interesting and would like to see some code samples.
|
Previous
Index
Next
Threaded
Edit
Reply
Quote
