31-07-2012, 10:03 AM
JavaBeans and JSP
JavaBeans4JSP.ppt (Size: 63 KB / Downloads: 31)
JavaBeans
The Java component technology
originally intended for the creation and management of “pluggable” GUI components; Java’s answer to Visual Basic’s VBX/OCXs
becoming more popular for encapsulating business logic for server-side applications (especially Java Server Pages
many Java GUI Development tools have been modified to allow application development of server-side applications (Visual Café, Jbuilder, VisualAge for Java) along with the development tools being delivered with application servers (SilverStream, BEA Weblogic)
A JavaBean is nothing more than a class that maintains some state data (called properties) and follows a certain set of coding conventions. Along with certain Java runtime support (reflection and introspection) can JavaBeans can be easily added to and maintained by most of the Java GUI Development Tools .
API requires that:
Must implement java.io.Serializable or java.io.Externalizable
Beans must be able to support their own persistence
this allows the bean to be saved and restored consistently
provide a no-arguments constructor
provides a single way for the Bean to be instantiated
insures consistent bean creation and initialization
private properties must have corresponding get/set methods that follow the appropriate naming patterns
each piece of state data to be exposed is called a property
made public via accessor and mutators (setters and getters)
accessor methos names must start with “get”
for property int color the accessor would be getcolor()
mutator methods names must start with “set”
for property fuelCapacity the mutator would be setfuelCapacity()
Environmental Support
To use JavaBeans with JSP no environmental support is needed, but for a better understanding of JavaBeans in the whole we’ll take a look…
Introspection ( java.beans.Introspector) defines the resources that allow the programatic construction of information on the Bean
facilitates the discovery of properties and methods by inspecting the .class file
can be done two ways : the reflection APIs or by providing a java.beans.BeanInfo class with the bean to describe the public methods and properties,
Reflection (java.lang.reflect) a set of resources that allows a program to discover the public properties and methods of classes that have been loaded by the class loader
this is facilitated by the naming convention for accessors and mutators (i.e. the names must start with “get” or “set”)
don’t need to need to knownames of properties as long as we know the names of the accessor and mutators
These environmental support mechanisma allow the JavaBeans to be cleanly integrated into GUI based, Java Development tools like VisualCafe, VisualAge and Jbuilder.