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.
There is nothing to stop you calling init() from service(), but one has to wonder why you would want to do so. If you expect your servlet might be subclassed (particularly by a different developer) in the future, it would be wise to avoid calling init() from service() because this would surprise them and perhaps cause bugs.
Betty Rubble? Well, I would go with Betty... but I'd be thinking of Wilma.
Even if u call it in ur code it won't do 'nething for you.
It will do whatever is coded in it, no? You might want a servlet to re-read configuration from a file or refresh a cache from the database so you don't have to stop and restart the server to affect changes. Even so, I'd make a method with a more meaningful name like loadFooCache() and call it from init() and from the refresh() call.
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi