The following sections describe how to configure JavaServer Faces (JSF) and JSP Tag Standard Library (JSTL) with WebLogic Server.
JSF 1.2 (JavaServer™ Faces) and JSTL 1.2 (JSP™ Standard Tag Library) packages are bundled with WebLogic Server as shared Web application libraries. These libraries can be referenced by standard Web applications that use JSF or JSTL functionality.
For information on referencing these shared libraries with your Web applications, see Developing Applications with WebLogic Server.in
JavaServer Faces technology simplifies building user interfaces for JavaServer applications. Developers of various skill levels can quickly build web applications by: assembling reusable UI components in a page; connecting these components to an application data source; and wiring client-generated events to server-side event handlers.
For more information about JSF technology, see
The JavaServer Pages Standard Tag Library (JSTL) encapsulates as simple tags the core functionality common to many Web applications. JSTL has support for common, structural tasks such as iteration and conditionals, tags for manipulating XML documents, internationalization tags, and SQL tags. It also provides a framework for integrating existing custom tags with JSTL tags.
For more information about JSTL technology, see
The following packages are available as shared libraries:
The libraries are bundled as
WAR files and are located in the
/common/deployable-libraries directory. The JSF libraries include the JSTL
JAR files for convenience, so that if an application references a JSF library, it automatically gets JSTL support as well.
Separate JSF 1.2 and JSTL 1.2
JAR files and implementation
JAR files are also provided in the
/server/lib/api.jar file. You can reference these
JAR files for compilation purposes or when using other utilities while developing Web applications.
The following table lists the JSF 1.2 library file name and its
The following table lists the JSTL 1.2 library file name and its
Since JSF and JSTL libraries are provided as Web application libraries, they must be deployed before the Web application that is using JSF or JSTL functionality is deployed. The libraries can be deployed using the Administration Console or with the command-line
Here’s an example of deploying a JSF 1.2 library using the
java weblogic.Deployer -adminurl t3://localhost:7001
-user weblogic -password weblogic
This command deploys the JSF 1.2 library using the default
implementation-version defined by the
MANIFEST.MF in the library.
After a library is deployed, the
implementation-version of the library can be found in Administration console. This information can also be found in the
MANIFEST.MF file of the library
For more information on deploying a Web module, seein Deploying Applications to WebLogic Server.
To reference a JSF or JSTL library, a standard web application can define a
<library-ref> descriptor in the application’s
weblogic.xml file. Here is an example:
For more information on referencing a Web application library, see Developing Applications with WebLogic Server.in
JSF 1.1 and JSTL 1.1 packages are also bundled with Weblogic Server 10.0 as shared libraries. Existing Web applications that use JSF 1.1 and JSTL 1.1 functionality can run on the Weblogic Server 10.0. You can choose the appropriate JSF or JSTL library based on your Web application.
For more information on the supported JSF 1.1 and JSTL 1.1 libraries, seein the WebLogic Server 9.2 documentation.