|
|
This section describes the contents and organization of this guide—Developing Web Applications, Servlets, and JSPs for WebLogic Server
This document is a resource for software developers who develop Web applications and components such as HTTP servlets and JavaServer Pages (JSPs) for deployment on WebLogic Server®. This document is also a resource for Web application users and deployers. It also contains information that is useful for business analysts and system architects who are evaluating WebLogic Server or considering the use of WebLogic Server Web applications for a particular application.
The topics in this document are relevant during the design and development phases of a software project. The document also includes topics that are useful in solving application problems that are discovered during test and pre-production phases of a project.
This document does not address production phase administration, monitoring, or performance tuning topics. For links to WebLogic Server documentation and resources for these topics, see Related Documentation.
It is assumed that the reader is familiar with J2EE and Web application concepts. This document emphasizes the value-added features provided by WebLogic Server Web applications and key information about how to use WebLogic Server features and facilities to get a Web application up and running.
web.xml schema under the root element <web-app>.
This document contains Web application-specific design and development information.
For comprehensive guidelines for developing, deploying, and monitoring WebLogic Server applications, see the following documents:
In addition to this document, BEA Systems provides examples for software developers within the context of the Avitek Medical Records Application (MedRec) sample, discussed in the next section.
MedRec is an end-to-end sample J2EE application shipped with WebLogic Server that simulates an independent, centralized medical record management system. The MedRec application provides a framework for patients, doctors, and administrators to manage patient data using a variety of different clients.
MedRec demonstrates WebLogic Server and J2EE features, and highlights BEA-recommended best practices. MedRec is included in the WebLogic Server distribution, and can be accessed from the Start menu on Windows machines. For Linux and other platforms, you can start MedRec from the WL_HOME\samples\domains\medrec directory, where WL_HOME is the top-level installation directory for WebLogic Platform.
WebLogic Server optionally installs API code examples in WL_HOME\samples\server\examples\src\examples, where WL_HOME is the top-level directory of your WebLogic Server installation. You can start the examples server, and obtain information about the samples and how to run them from the WebLogic Server Start menu.
BEA provides several Web application, servlet, and JSP examples with this release of WebLogic Server. BEA recommends that you run these Web application examples before developing your own Web applications.
For this manual, WebLogic Server introduces the following improvements for version 9.2:
| Note: | WebLogic Server changed substantially in version 9.0, and these changes apply to later releases as well. |
Just as standard shared J2EE applications can be deployed to WebLogic Server as application-libraries, a standard Web application can be deployed to WebLogic Server as a webapp-library so that other Web applications can refer to these libraries. For information on referencing these WebApp libraries with your Web applications, see Using WebApp Libraries With Web Applications in Developing Applications with WebLogic Server.
Three JSF (JavaServer™ Faces) and JSTL (JSP™ Standard Tag Library) packages are bundled with WebLogic Server as WebApp libraries. These libraries can be referenced by standard Web applications that use JSF or JSTL functionality.
The following three packages are being made available as WebApp libraries in release 9.2:
See Using JSF and JSTL With Web Applications.
When using generic proxy servlets, you can define the KeyStore initialization parameters to use two-way SSL with your own identity certificate and key. For more information, refer to the following documents:
The
Servlet 2.4 specification allows you to define the authentication method (BASIC, FORM, etc.) to be used in a Web application. WebLogic Server 9.2 provides an auth-method security module that allows you to define multiple authentication methods (as a comma separated list), so the container can provide a fallback mechanism. Authentication will be attempted in the order the values are defined in the auth-method list.
See Providing a Fallback Mechanism for Authentication Methods in Programming WebLogic Security.
In general, WebLogic Server processes incoming HTTP requests and the response is returned immediately to the client. Such connections are handled synchronously by the same thread; however, some HTTP requests may require longer processing time. Handling these requests synchronously causes the thread to be held, waiting until the request is processed and the response sent. To avoid this scenario, WebLogic Server provides two classes that handle HTTP requests asynchronously by de-coupling the response from the thread that handles the incoming request.
See A Future Response Model for HTTP Servlets.
The docHome parameter for FileServlet has been deprecated.Use virtual directories as an alternative.
|