Lots of whitepapers have suggested that JSP, merely reversed the age old known problem of HTML intermingled in Java code, in the old days you had servlets with HTML code calcualtions, now you have JSP/HTMl with Java code, pretty much. Simple put if you use JSp as is without your own taglibs then you are surely reversing the old age problem of mixed code languages. However, if you use a taglib that you have developed for your in house applications that appropriately abstracts out the rendering/HTML part, and leaves your JSP pages to be nothing but a very simple XMLish page with taglib elements having data set upon them, hence moving it closer to the MVC model. Further, to really take advantage of the solution, is to include XML description of thoise taglibs and hence allowing the taglib behaviour to vary without rebuilding your taglib code, thats great, of course you wouldnt do it for everything but only for those very very dynamic pages/section of the application, since XML slows thigns down. Then if you are concerned about speed well here it is interesting how you develope your XML descriptors of your pages, wither you use XSLT to parse them or a good traditional XML parser and tune it for your application, personally I stayed away from XSLT implementation since it involves maitaing yet another file.
So the ultimate solution is, for the ultimate 80% of your JSPs are utilising static JSP tags froma "static" taglib that you have written, and then 20% of the other taglibs would go against XML based tags taglib. This approach could be coined out as JSP Model to with XML descriptor usage.
Anyone interested in learning more about this, email me back.
Emad J. Benjamin.