This section gives an overview of the functionalities that are added or changed in the Servlet and JSP specifications, and also describes the support range of functionalities in Application Server.

For details on operations and precautions when using the functionalities that are added or changed in different versions of Servlet specifications and JSP specifications in Application Server, see the sections starting from 6.2.3.

The following table gives an overview of the functionalities that are added, or changed in Servlet 3.0 and describes the support range.

Table 6-1 Overview of the Servlet 3.0 functionalities and the support range

No.	Functionality name	Functionality overview	Support
1	web.xml (Servlet 3.0) and new annotations	You can use a web.xml that is compatible with Servlet 3.0.	Y
		You can define servlet annotations. (web.xml can be omitted)	Y
		You can use web-fragment.xml.	N #1
2	Dynamic servlet definition	You can define servlet, filters or listeners with an API.	Y
3	File upload	Requests with multipart/form-data as the content-type can be processed.	Y
4	Static resource allocation	You can allocate static resources or JSP to META-INF/resources of the JAR file.	Y
5	Security enhancements	You can set security with annotations. You can use APIs for authentication.	Y
6	Asynchronous servlet	Request processing and response generation can be done in a different thread other than the thread that receives requests.	N #2
7	Other changes in the Servlet specifications	You can add the HttpOnly attribute to Cookie.	Y
		You can change the HTTP Cookie name indicating a session ID of the HTTP session.	Y
		You can use the HTTP digest authentication.	N #3
		You can acquire the SSL Session ID as the ServletRequest property.	N #4
8	Changes in JSP specifications	You can use a web.xml to specify the default content type or the buffer size.	N #5
9	Methods with the EL parameter	You can invoke methods having parameters.	Y#6
10	API enhancements	You can use newly added or changed APIs.	L#7

Legend:

Y: Supported

N: Not supported

L: Limited support

#1

Is ignored, if the Web application includes web-fragment.xml.

#2

The DD and annotations related to asynchronous servlets are ignored. An exception is thrown if you invoke an API of an asynchronous servlet.

#3

Operation is not guaranteed if you set the digest authentication in the DD.

#4

If you specify javax.servlet.request.ssl_session_id as an argument in the ServletRequest class and invoke the getAttribute method, null is always returned.

#5

A web.xml compatible with JSP 2.2 can be read. However, any tag added in JSP 2.2 is ignored.

Even for a Web application of version 3.0, the JSP version that complies with JSP is version 2.1.

#6

You cannot use the Expression Language of JSP 2.2 if the EL is of the JSP 2.1 or 2.0 specifications. If you use an API of JSP 2.2 EL, the operation is not guaranteed because the API is not checked.

#7

You can use APIs of supported functionalities, but not of functionalities that are not supported. For details on APIs of Servlet 3.0, see 6.2.3(9) About APIs.