|
![]() |
![]()
A JSP application collects pages, scripts and Java Beans into a self-contained web application. Applications are just generalized virtual hosts, only based on the URL instead of the host name. For example, a bulletin board application groups pages for article reading, group listing, user registration, and new article posting into a single application. Applications can keep track of user sessions, giving the users the illusion of a single application out of disjoint pages.
Many, if not most sites, will only use the default application.
JSP applications can group common functions and classes into script files, organizing and simplifying the application. The individual pages can then import the common scripts to use them. JSP pages can focus on HTML presentation and the script libraries can concentrate on the content. As described in the import documentation, Resin searches for imported scripts along a SCRIPTPATH. For JSP pages, the SCRIPTPATH looks in the application script directory first, then in the global libraries.
Java Beans get first class treatment in JSP 1.0. Beans can be created for a page, across a session, or for the entire application. The classes and lib directories can contain application beans used by jsp:useBean. These are simply Java classes implementing the bitmechanic work of an application. For example, a shopping cart application may have a set of Java classes that perform the security necessary for credit card processing. The application can put those classes in the beans directory and access them from the JSP page. Beans can be created with different lifetimes.
Accessing BeansEach bean is defined with a jsp:useBean directive.JSP assigns the created bean object to the JavaScript variable named by jsp:useBean. In addition, the created beans are stored in JSP variables: page
beans are stored in
Session variables let applications keep track of the user as she moves through the site. Any e-commerce site needs this capability to keep track of the user's purchases. JSP sessions start when the page accesses the session variable. If a page never uses sessions, the jsp:session:onStart code will not execute and the web server will not send the client any cookies. Sessions end when the session times out, when the session is invalidated, or when the application ends. Resin locks the session variable before executing the page. So JSP applications don't need to worry about synchronizing the session variable.
|