This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I have read a lot on this topic in the forums but never got a conclusive answer.
Say I have some initialization functionality. Say i decide to initialize the same in the servlet's no args constructor instead of the regular init method. Both are called only once during the life time of the servlet.
So whats the advantage of having all inside a init method. To be precise what i want to know what were the perils of the no args (not parameterized)servlet constructor approach which caused the creators of servlets to resort to the init method approach.
Is there some handshake between the container & the init method which is not in the case of servlet's no arg constructor
It is guarenteed that the servletConfig instance is set up when the init() method is called.
When it comes down to it, it's always best to do things in the standard manner. Just because you might seem to be able to get away with something like setting up in a constructor, that's no guarentee that things won't break later when an underlying assumption changes.
It's your foot; you can choose whether to shoot at it or not.