Develop servlets with WAS extensions

 

Overview

Several WAS extensions are provided for enhancing your servlets. This task provides a summary of the extensions that one can utilize.

 

Procedure

  1. Review the supported specifications.

    Create Java components, referring to the Servlet specifications from Sun Microsystems.

    See Resources for learning for links to coding specifications and examples.

    The application server includes its own packages that extend and add to the Java Servlet Application Programming Interface (API). These extensions and additions make it easier to manage session states, create personalized Web pages, generate better servlet error reports, and access databases. Locate the Javadoc for the application server APIs in the product install_root\web\apidocs directory.

    All the public WAS APIs are located in the com.ibm.websphere... packages.

  2. Use your favorite integrated development environment (IDE), or a text editor, to develop or migrate code artifacts that meet the specifications.

  3. Test the code artifacts.

 

What to do next

Assemble your code artifacts into a Web module using assembly tools as a prerequisite to deploying the code to the application server.

 

See also


Application life cycle listeners and events
Listener classes for servlet context and session changes
Example: com.ibm.websphere.DBConnectionListener.java
Servlet filtering
Filter, FilterChain, FilterConfig classes for servlet filtering
Example: com.ibm.websphere.LoggingFilter.java
Configuring page list servlet client configurations
autoRequestEncoding and autoResponseEncoding
Examples: autoRequestEncoding and autoResponseEncoding encoding examples

 

See Also


Servlets

 

Related Tasks


Migrating Web application components from WebSphere Application Server V4.x

 

See Also


Web applications: Resources for learning