I think this JSP technology is going to catch fire soon if it hasn't already (it's new for me). It's perfect for separating (AKA de-coupling) presentation (View) from program logic (Model). Programmers can do what they do best writing Java Beans (Enterprise or otherwise) and Web page designers can concentrate on how to present the data to the end users via HTML and JSP. Sun re-organized their site over the weekend and now they have this: A beginner's guide to using the JavaServer Pages technology: http://java.sun.com/products/jsp/docs.html
Tony Alicea Senior Java Web Application Developer, SCPJ2, SCWCD
My own feeling is that JSP is a good idea poorly implemented. It is almost impossible to debug a complex JSP because the errors are occuring in the generated servlet. A missing ! can totally screw up the page without giving any obvious error message. We use servlets to create a Hashtable which is fed into a java class that merges the data from the Hashtable with an HTML file. We get the decoupling without having to worry about the HTML page designer accidentally screwing up our JSP tags.