Yeah. A JavaBean IS a class. It is a specialized class. If you follow the rules for making JavaBeans it will make your life easier that just making the class your way. It does things for you. Example JavaBean:
public class MyString {
String str1;
public void setStr1(String s){str1 = s;}
public void getStr1(String s) {return str1;}
}
Now in your JSP you can use this:
<html><body>
<jsp:useBean name="MyString1" class="MyString">
<jsp:setProperty name="MyString1" property="str1" value="I">
Here is my string: <jsp:getProperty name="MyString1" property="str1">
</body></html>
Notice that I never call the methods getStr1() or setStr1() in the JSP. How does it know which method to call? Simple. If you follow the pattern of making your metod names set + " capped variable name" or get + "capped variable name", the JSP will know what to do. It knows because you put in jsp:getProperty or jsp:setProperty. It puts two and two together for you. If you do not do this, things will get more difficult for you. Much more difficult. This is one advantage to creating a class in a JavaBean format.
Remember, a JavaBean IS a class. It is just a class that follows certain rules as to how it is written. Those rules help it do its specific role in a MVC environment.
Enjoy!
