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.
Originally posted by eswar kumar: what are the optimum no of servlets required for a project?
there's no optimum number of servlets. It all depends on how you architecture your application and how complex it is. You can use a single servlet to do *all* tasks if you want, but at the end you'll find yourself in a complete chaos
I'm not going to be a Rock Star. I'm going to be a LEGEND! --Freddie Mercury
so it depends on if you want to put all your code in servlets or not. if you do then each servlet should have a very specific task. if there are multiple pages that do the same sort of thing then they can be done in the same servlet, but very different pages should have their own. if you have shared functions accross different pages then you need to abstract the code into classes and use it accross the different servlets.
Kim Jong II (North Korea's Dear Leader) said:Nuclear weapons don't kill people, people kill people.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com