Mvc - connection pool - jstl - oh my!

Question

I am trying to understand how to use the mvc model to break my existing jsp's up. I finally got my connection pool working yesterday(yay!) so now I want to get everything organized into servlets. My understanding of servlets sucks - and I have not written one yet. Researching it on the net hasnt helped much - a bit overwhelming..
Please tell me if my logic is on track or not - keeping in mind the mvc model - keeping in mind I dont know how to write a servlet : )
DATABASE package;
public static dbpool getConnection() {
     // write JNDI information
public static void dbpoolClose(Connection connDB) {
     // close connection
}Then in a servlet I would try to write something like this...
MyBean {
// call the connection method
- do crud operations
- use getters and setters
- close statements that I have open
// call the close connection method
}Then in my JSP( I have JSTL working YAY!!) I wil call the bean/getters/setters and use JSTL to manipulate and present the data? Is this close to being in the MVC model?
I havent found an example using the mvc using a connection pool, database operations and a jsp - that I have been able to understand.. so If I am waay off.. sorry.

Answer 1

Basically, use the servlet to tell other classes what to do (these can be other servlets or whatever).
Those classes prepare the data you want to have the JSPs show and process the data returned from the JSPs.
The JSP does nothing except display data presented to it by the servlet (and may have URLs or forms to provide input to servlets.
At its simplest, there's no controller at all (so no C). A JSP calls a servlet which processes the data sent to it and prepares new data for another (or the same) JSP to which it forwards the request when done.
That data can be stored in the Http session or (sometimes) better in the request.
More usually, a controller will receive all requests from and determine to what servlet to send them.
The servlet then either determines on its own to which JSP to send the results or gives those results back to the controller which will do that for them and forward to the proper JSP.
If needed you can thus chain requests so that a request goes to a servlet, from there to another servlet and then to a JSP (for example), each time via the controller.
This can be handy to break up complex processing in small steps where those small steps could also occur separate.