Tutorials
WebSphere
WebSphere V5.0 : Web Development - Work with Web Application Deployment Descriptor
WebSphere V5.0 : Web Development - Work with Web Application Deployment Descriptor - Page 2
WebSphere V5.0 : Web Development - Work with Web Application Deployment Descriptor - Page 3
Lets you add or remove welcome and error page to the deployment descriptor. Also allows you to define the login-config element.

Lets you add or remove servlet context initialization parameters for a Web applications. The context parameters apply to all servlets within the application.

Lets you add or remove mappings between the extension types and MIME types (such as text/plain). File extensions are strings that describe an extension without the dot (.) delimiter (for example, txt).

Extensions
Lets you specify settings for WebSphere extensions (such as enabling reloading).

Source
Lets you edit the web.xml source directly.

Editing the XML source directly is not the recommended method for editing the deployment descriptor. The best way to build deployment descriptor files is to edit the multiple tabbed pages. As you specify deployment information in these tabbed pages, the editor automatically incorporates the appropriate XML tagging.
In addition to the configuration information in the web.xml file, other deployment descriptors in a Web project include the following information:
Binding information — information is required by the application server to bind the deployment information specified in the application to a specific instance. For example, it may map a logical name of an external dependency or resource to the actual physical JNDI name of the resource. It also may map security role information to a set of groups or users.
IBM binding and extensions information (ibm-web-bnd.xmi and ibm-web-ext.xmi files) — additions to the standard descriptors for J2EE applications, Web applications, and enterprise beans. The extensions enable Enterprise Edition or legacy (older) systems to work in the current WebSphere Application Server environment. They are also used to specify application behavior that is vendor-specific, undefined in a current specification, or expected to be included in a future specification.
_____________
Author: Mikalai Zaikin. Please Click Here to visit Authors site for any updates and changes to the study notes.
First Page: WebSphere V5.0 : Web Development - Work with Web Application Deployment Descriptor