Overriding doPost() better than service() method

Question

why overriding doPost() or doGet() is better than service() method
in servlets
thanx

Answer 1

One reason is to help break your code up into more manageable pieces. For example, let's say you have a page that displays a list of Employees when called via GET, but also includes a FORM that lets you delete employees based on checkboxes included on the form with a SUBMIT button. If you use the doService, you'll probably have to do something like this:
doService(request, response) {
  if (request.getMethod().equals("get")) {
    // handle GET logic
  else {
    //  handle POST logic
}However, if you have two separate methods, it makes the logic a little simpler. For example:
doGet(request, response) {
  // handle GET logic
doPost(request, response) {
  // handle POST logic
}The distinction is fairly minor, but I do think the code is cleaner without having to check for gets and posts. With that said, I have plenty of servlets that use the doService() method because there is no distinction in those servlets between the doGet() and doPost() functionality.
Michael