>
> You don't need more then one servlet for one application.
> Use method HttpServlet.service() instead of doGet() or doPost(),
> use HttpServletRequest.getPathInfo() or existence of some parameters
> to distinguish what page to show.
>
I would seriously question the idea that you never need more than
one servlet per application. You should plan on having one servlet for each
task that is part of the application and if you abstract things properly you
can
reduce this number usually.
It is also a bad idea to override the servlet service method as that is
usually
implemented by the ServletEngine vendor to route requests to the right
place.
If you try and have one servlet that does all you are placing all your eggs
in one basket.
You will end up with a large, hard to maintain and badly implemented servlet
that
will never end up doing things as you it to in the first place.
Andy Bailey
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
