Screaming Penguin - Source Does Matter

Javaworld has a article about the RIGHT way to use JSP. Its an older article but it still applies. Its all JSP using MVC and the "memento" design pattern.

JSP can be very elegant, clean and easy to maintain. Or alternatively it can be a mess beyond all proportion. My personal goal recently was to build some example JSP and totally separate logic from presentation. Using the examples from this article with a few tweaks (utility "beans" for validate, etc) that can be accomplished.

This article is not exactly how it should be done, but its 98% there and the rest is obvious. Once using this type system there is no configuration mess as with servlets (no app deployment descriptors, etc) and web developers can create all the front end with knowing only three basic JSP commands (usebean, get, set.)

This method is IMHO even better than servlets by far. As we all know, JSPs are servlets, but in this method you can write beans and even processing JSP pages (pages that are never displayed to user) to accomplish virtually any task a servlet can pull off its far easier to work with and maintain (no on off modes for the app server, no restarting to test new servlet, no maintenance of servlets to jsps, etc.)

For more info check the link --->   Advanced Form Processing with JSP: JavaWorld