NonStop Servlets for JavaServer Pages (5.0) System Administrator's Guide

Migrating to NSJSP 5.0
NonStop Servlets for JavaServer Pages (NSJSP) System Administrator’s Guide525644-002
7-11
Changes from Servlet 2.3 to Servlet 2.4
In the Deployment Descriptor web.xml, all sub-elements under the <web-app>
element can be in any order.
In the schema for the deployment descriptor web.xml, the <url-pattern>
element under the <web-app>/<security-constraint>/<web-resource-
collection> element tree is mandatory and must always be specified.
Allows multiple constraints on pattern and method (specified using <url-
pattern> and <http-method> elements in the deployment descriptor
web.xml).
Multiple constraints on pattern and method (specified with <url-pattern> and
<http-method> elements in the deployment descriptor web.xml are now
supported and the constraints applied to the web application is the resultant set
defined by combining the individual constraints.
The container throws HTTP Error 500 (Internal Service Error) for the entire web
application for any unhandled exceptions in the Application Listener code.
The deployment descriptor web.xml defines Servlets using the <welcome-file>
element under the <web-app>/<welcome-file-list> element tree.
Clarifications for always alive sessions (sessions that never time out).
In the schema for the deployment descriptor web.xml the <session-timeout>
element under the <web-app>/<session-config> element tree supports
sessions that never time out (that is , sessions can have zero or negative values).
The container now returns SC_NOT_FOUND (404) codes on direct access to
/WEB-INF/ and /META-INF/ resources.
See the Java Servlet 2.4 API documentation for more information
http://java.sun.com/products/servlet/.