simple and classic tags
posted 8 years ago
Yes, I guess so. In the wider scheme, although Servlet, GenericServlet, ServletRequest, ServletResponse can be used to implement any protocol, in practise containers usually only implement HTTP. Although it could be very useful to have the containers also implement FTP or any other popular protocols, they very often don't. So that means effectively all the "generic" interfaces are unused directly, and you always end up using the javax.servlet.http.* classes in your apps. Having JspContext around just means you have to cast it to PageContext whenever you need to access anything HTTP-specific, and that's a real pain. Also I just can't imagine ever needing to use JSPs (the presentation components of Java EE) on anything other than HTTP(S). So my point of view is that usually everything you do in Java EE Web is designed for use with HTTP(S).