This week's book giveaways are in the Refactoring and Agile forums.
We're giving away four copies each of Re-engineering Legacy Software and Docker in Action and have the authors on-line!
See this thread and this one for details.
Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Agile forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

when attributes are beans

 
samdeep aarzoo
Ranch Hand
Posts: 160
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
can anyone explain in detail
when attributes become beans???
 
Sergey Tyulkin
Ranch Hand
Posts: 87
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Bean is an object that follows JavaBeans programming methodology.
The simplest bean has private attributes and so-called getters and setters. They are the methods, which get the property and set it.
The more complicated bean has also some events and event listeners attached, but they are not used usually in web applications.

So, every attribute, that follows JavaBeans methodology is a bean; and that's why the answer to question "when attributes become beans?" is "when developer developes the attribute classes to be beans".
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic