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.
Why do we have to override init() method in Servlets while we can do the initialization in the constructor and have web container call the constructor passing ServletConfig reference to servlet while calling constructor?
Ofcourse container has to use reflection for this but container has to use reflection anyway to call a simple no-arg constructor
Since a constructor can not be part of an interface, it can not be “formally” specified within the Servlet API, unlike normal methods. Moreover, since Java has no destructors, a
destroymethod is needed anyway, so it defining the correspondinginitmethod makes the API more consistent and easier to use.Using reflection to detect/verify constructor parameters would just unnecessarily complicate things, and I don’t see any added value.