JavaBeans components are architectural elements of multitier JSP applications. JavaBeans are typically used as part of a middle "business-logic" layer meant to separate the presentation logic from data-access logic. In these applications, the JavaBeans, (also referred to as "beans") not the JSP pages, contain the logic that directly accesses the database.
In Dreamweaver, JavaBeans components are treated as sources of dynamic content for JSP pages, and appear in the Bindings panel. You can double-click JavaBeans in the Bindings panel to view their properties, and then drag the properties to the page to create dynamic data references.
You can also define a JavaBeans collection (a set of JavaBeans) as a source of dynamic content. However, Dreamweaver supports only repeated regions and dynamic bindings when using JavaBeans collections.
Copies of the bean class (or of the .zip or .jar file containing the bean class) must reside in the following locations:
If Dreamweaver and the application server are both running on the same system, and the application server uses the system class path (not an internal class path), a single copy of the JavaBeans class can reside on the computer in the system class path. Both the application server and Dreamweaver will use this copy of the class. Otherwise, copies of the JavaBeans class must reside in two paths on the computer (as described above).
The folder structure must match the JavaBeans package. For example, if the JavaBeans package is called com.ardvark.myBean
, then the package must be stored in /com/ardvark/ within the class path or in the Dreamweaver Configuration/classes folder.
The JavaBean dialog box appears.
For instructions, click the Help button on the dialog box.
The JavaBean Collection dialog box appears.
For instructions, click the dialog boxs Help button.