This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Java class : A java class is a class which normally has properties and methods through which these properties are modified. The class can perform some functions specific to the data in the class.
Java Bean: java bean is also a java class but its basic use is for storing the state of the class , i.e it has properties and there are setter and getter methods. This class is basically used for storing the state of the data and then retreiving the state at a later point of time. Even java bean is also a class. java bean can be said as a class which normally does not have processing logic. It is however not illegal if the java bean contains processing logic. regards shekar.
I think there's one more requirement in the definition of Java Bean, and that's a "default constructor" - one with no arguments. The idea with all the get and set methods is that you can "inspect" a bean through the reflection APIs and discover all those methods. Tools like IDEs could accept a new bean they've never heard of before, figure out all the get and set methods and build a properties sheet and integrate the bean quite nicely. I don't know how much this technology caught on, but I think not near as much as the inventors hoped. If you haven't heard of reflection, trust me it's cool, it's a bit advanced, and one day you'll have a ball with it. You'll also hear about Enterprise Java Beans. Something else altogether, not related, very different (am I making the point) not the same thing.
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi