Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What is the difference between request dispatcher’s forward method and the concept of servlet chaining?
Example
RequestDispatcher rd= req.getRequestDispatcher("pathToServlet");
rd.forward(req,resp);
What this does is forwards the request without involving the client(browser) interaction. But can we achieve the same using Servlet Chaining?. If we can then what is the difference?.
It’s not different. “Servlet chaining” is just a term coined in dark J2EE 1.1/1.2 ages when servlet filters didn’t exist. Indeed, it’s basically the approach of using
RequestDispatcher#forward()to forward from one to other servlet (and ensuring that the response isn’t already committed as that would otherwise result inIllegalStateException).Since J2EE 1.3 (Servlet 2.3, over a decade ago already!) servlet filters were introduced which made the process so much more clean and easy. Since then, “Servlet chaining” is frowned upon and usually marked as “bad design”. These days, you’d ultimately like to end up with only one front controller servlet and several business models.