iTP Secure WebServer System Administrator's Guide (iTPWebSvr 6.0+)

Using NonStop Servlets for JavaServer Pages
(NSJSP)
iTP Secure WebServer System Administrator’s Guide—523346-002
9-47
Changes from Servlet Version 2.1 to 2.2
Changes from Servlet Version 2.1 to 2.2
Deprecated Methods
•
Constructor javax.servlet.UnavailableException.UnavailableException(Servlet
servlet, String message)
•
Constructor javax.servlet.UnavailableException.UnavailableException(int
sec,Servlet servlet, String message)
•
Method javax.servlet.http.HttpSession.getValue(String name)
•
Method javax.servlet.http.HttpSession.getValueNames()
•
Method javax.servlet.http.HttpSession.setValue(String name, Object value)
•
Method javax.servlet.http.HttpSession.removeValue(String name)
Other Changes
According to the Servlet 2.2 specification, there are two ways for a servlet application
to invoke the getRealPath method:
•
Use the ServletRequest.getRealPath, which has been deprecated
•
Use ServletContext.getRealPath.
In previous releases of the iTP Secure WebServer the getRealPath always relied
on the httpd server to resolve the path. In order to properly identify the path, the
servlet.ssc needs to provide the httpd server with the server port and server name.
In the NSJSP release, the server port and server name information is known only
at the request level. Due to this limitation, the servlet.ssc will not be able to invoke
httpd server if the getRealPath method is from the context level.
What this implies is that the resource known to the httpd server will not be
identified if the getRealPath method is invoked from the context level, where it is
resolved locally and thus may not be correct.