GenericServlet vs HttpServlet
1>>>>>>>>
Difference between HttpServlet vs Generic Severlet
j
avax.servlet.
Servlet
----
is an interface defining what a servlet must implement.it defines methods for all the implementations - that's what interfaces usually do.
javax.servlet.GenericServlet------ is just that, a generic, protocol-independent servlet. It is abstract, so it is not to be directly instantiated. It is the usable class to extend if you some day have to write servlet for protocol other than HTTP.
javax.servlet.http.HttpServlet------- is abstract class to be extended if you want to communicate over HTTP protocol. Most likely you only have to care about this one.
Servlet:-
- The Servlets runs as a thread in a web-container instead of in a seperate OS process.
- Only one object is created first time when first request comes, other request share the same object.
- Servlet is platform independent.
- Servlet is fast.
GenericServlet:-
- General for all protocol.
- Implements Servlet Interface.
- Use Service method.
HttpServlet:-
- Only for HTTP Protocol.
- Inherit GenericServlet class.
- Use doPost, doGet method instead of service method.
2>>>>>>>>
HttpServlet
- public abstract class HttpServlet
- extends GenericServlet
- implements java.io.Serializable
Provides an abstract class to be subclassed to create an HTTP servlet suitable for a Web site. A subclass of HttpServlet
must override at least one method, usually one of these:
doGet
, if the servlet supports HTTP GET requestsdoPost
, for HTTP POST requestsdoPut
, for HTTP PUT requestsdoDelete
, for HTTP DELETE requestsinit
anddestroy
, to manage resources that are held for the life of the servletgetServletInfo
, which the servlet uses to provide information about itself
Constructor Summary | |
HttpServlet() Does nothing, because this is an abstract class. |
Method Summary | |
protected void |
doDelete(HttpServletRequest req, HttpServletResponse resp) Called by the server (via the service method) to allow a servlet to handle a DELETE request. |
protected void |
doGet(HttpServletRequest req, HttpServletResponse resp) Called by the server (via the service method) to allow a servlet to handle a GET request. |
protected void |
doHead(HttpServletRequest req, HttpServletResponse resp) Receives an HTTP HEAD request from the protected service method and handles the request. |
protected void |
doOptions(HttpServletRequest req, HttpServletResponse resp) Called by the server (via the service method) to allow a servlet to handle a OPTIONS request. |
protected void |
doPost(HttpServletRequest req, HttpServletResponse resp) Called by the server (via the service method) to allow a servlet to handle a POST request. |
protected void |
doPut(HttpServletRequest req, HttpServletResponse resp) Called by the server (via the service method) to allow a servlet to handle a PUT request. |
protected void |
doTrace(HttpServletRequest req, HttpServletResponse resp) Called by the server (via the service method) to allow a servlet to handle a TRACE request. |
protected long |
getLastModified(HttpServletRequest req) Returns the time the HttpServletRequest object was last modified, in milliseconds since midnight January 1, 1970 GMT. |
protected void |
service(HttpServletRequest req, HttpServletResponse resp) Receives standard HTTP requests from the public service method and dispatches them to the do XXX methods defined in this class. |
void |
service(ServletRequest req, ServletResponse res) Dispatches client requests to the protected service method. |
why httpservlet is abstract?
If you extend the httpservlet class without overriding any methods, you will get a useless servlet;
GenericServlet
public abstract class GenericServlet
extends java.lang.Object
implements Servlet, ServletConfig, java.io.Serializable
Constructor Summary | |
---|---|
GenericServlet() Does nothing. |
Method Summary | |
---|---|
void |
destroy() Called by the servlet container to indicate to a servlet that the servlet is being taken out of service. |
String |
getInitParameter(String name) Returns a String containing the value of the named initialization parameter, or null if the parameter does not exist. |
Enumeration |
getInitParameterNames() Returns the names of the servlet's initialization parameters as an Enumeration of String objects, or an empty Enumeration if the servlet has no initialization parameters. |
ServletConfig |
getServletConfig() Returns this servlet's ServletConfig object. |
ServletContext |
getServletContext() Returns a reference to the ServletContext in which this servlet is running. |
String |
getServletInfo() Returns information about the servlet, such as author, version, and copyright. |
String |
getServletName() Returns the name of this servlet instance. |
void |
init() A convenience method which can be overridden so that there's no need to call super.init(config) . |
void |
init(ServletConfig config) Called by the servlet container to indicate to a servlet that the servlet is being placed into service. |
void |
log(String msg) Writes the specified message to a servlet log file, prepended by the servlet's name. |
void |
log(String message, Throwable t) Writes an explanatory message and a stack trace for a given Throwable exception to the servlet log file, prepended by the servlet's name. |
abstract void |
service(ServletRequest req, ServletResponse res) Called by the servlet container to allow the servlet to respond to a request. |
3>>>>>>>>
When we should use Service() or toGet(), toPost()?
The differences between the doGet()
and doPost()
methods are that they are called in theHttpServlet
that your servlet extends by its service()
method when it recieves a GET or a POST request from a HTTP protocol request.
A GET request is a request to get a resource from the server. This is the case of a browser requesting a web page. It is also possible to specify parameters in the request, but the length of the parameters on the whole is limited. This is the case of a form in a web page declared this way in html: <form method="GET"> or <form>.
A POST request is a request to post (to send) form data to a resource on the server. This is the case of of a form in a web page declared this way in html: <form method="POST">. In this case the size of the parameters can be much greater.
The GenericServlet
has a service()
method that gets called when a client request is made. This means that it gets called by both incoming requests and the HTTP requests are given to the servlet as they are (you must do the parsing yourself).
The HttpServlet
instead has doGet()
and doPost()
methods that get called when a client request is GET or POST. This means that the parsing of the request is done by the servlet: you have the appropriate method called and have convenience methods to read the request parameters.
NOTE: the doGet()
and doPost()
methods (as well as other HttpServlet
methods) are called by the service()
method.
Concluding,
if you must respond to GET or POST requests made by a HTTP protocol client (usually a browser) don't hesitate to extend HttpServlet
and use its convenience methods.
If you must respond to requests made by a client that is not using the HTTP protocol, you must useservice()
.
This is how
|