Also, there are so many things you can do in code that you can't do easily on a JSP page, like do the equivalent of writing a subroutine to share common code!
Originally posted by Bear Bibeault:
This statement tells me two things. 1) You are still trying to do too much on the JSPs. Do the "heavy lifting" in the servlet controllers. When thinking of JSPs, the term "code" shouldn't even be coming to mind. And 2) you don't yet have a good grasp of the facilities that JSP offers. The custom action mechanism is a strong means to share "common code" across pages.
Originally posted by Jeff Albertson:
If I had to reduce it to one complaint, I guess I don't like the whole idea of writing JSP documents. I'd rather write Java code. I like the static type checking, rather than having to touch each link to see if the EL expression parses correctly. (Is this testinglaziness on my part? What do folks in this forum use to unit test their JSPs? Cactus? If so, what do your recommend?)