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.
Just a general question for you all. Is it better to develop java classes or java beans. I know that java beans are generally used for developing GUI applications( I have used them for developing with JSP's and Websphere studio). As I am using Visual Age for Java 3.5 creating beans is fairly easy as the bean info class is generated for you corectly if you follow the correct procedures. What I would like to know is there any advantages of using classes instead of beans and visa versa? Are there any performance issues etc. Thanks in advance Paul
To be precise, Java Beans are simply classes that follow certain rules. There should be nothing wrong with letting a tool generate beans for you. In general, when I am developing classes I try and adhere to the Java Beans get/set naming pattern ... using that convention also makes it easier to use Java reflection with your code. The BeanInfo class is not required for a Java Bean, though it is particularly useful for UI beans (such as labels, text fields, etc.).
What makes a bean a bean; why are they special? I've read that they are reusable software components, but that doesn't tell me much. When would you *use* them? Also, I get the sense that enterprise java beans are not the same as java beans. What is the scoop on that/ Thanks.