I think the one servlet to handle multiple operations is fine as long as
- the operations are trivial
- the operations are logically related.
In this case for CRUD operations on your business object, they are definitely logically related.
You say you created a seperate class which invoked the database, so your servlet would pretty much be just gather request parameters, and invoke that Data access class.
With what you have described here, I see no problem with keeping it as one servlet.
> If it is then i encounter a problem when trying to display the results. My operations class method creates a result set and uses a println to display each row in the database, how would i get this to output form the servlet?
The standard approach would be to have your operations class method return a List of objects being the result (rather than println)
You then set that list as a request attribute, to make it available to your
JSP.
Your JSP then iterates over the list of objects to display them.
That way you seperate your display logic (the JSP) from where the data is coming from (the database).