I'm ever more thinking of joining the JCP and submitting a JSR to remove the scriptlet functionality from JSP completely. What keeps me back so far is the bureaucracy of the JCP (I've better things to do with my time) and the fact that we've a mass of old style JSPs and controlling servlets at work that I don't fancy updating
Thanks for the replies- looks like I can't do what I want with jstl then - quite honestly I don't see the advantage to it unless one is using a strict mvc architecture...a page of jstl looks as messy as a sciptlet to me...better to use a custom tag
If you're going to do branching, exception handling, validating, database handling (sql) etc.. in your JSPs... then JSTL, custom tags, EL, and the like are just more technologies to have to learn and keep up with. Just use scriptlets and work in one language -- Java.
The point of these technologies is to help extract the heavy lifting from the JSPs and move it into Servlets, Beans, and, plain old Java classes.
There is still a place for Model1, IMHO. Prototypes, small - one developer apps, vaporware, etc can be thrown together very quickly this way. If the project is going to have multiple developers and/or web designers OR if it can possibly become a medium or large sized production app, then it makes sense to figure out how to use these tools to achive the kind of separation of concerns that allows a project to grow and be maintained without turning into spaghetti code.
PS: before anyone starts flaming... I mean no disrespect to Perl. I like it. It's funky, cool, and indespensible for unix administration. It just wasn't made for enterprise development efforts.... [ January 14, 2005: Message edited by: Ben Souther ]