On Fri, 6 Sep 2002, Joseph Ottinger wrote: > >However, the argument from "cognitive dissonance" seems unsubstantiated > >and a little fuzzy. What if, for instance, you predominantly design small > >applications? Or if you need to prototype applications, which typically > >involves a radically different procedure from production-track > >applications anyway? > > If there's no dissonance, go for it - but I'd say using methodology that > minimizes reuse isn't the best idea either.
I agree; reuse is important. I'm hoping that JSP 2.0's adoption will make it easier to reuse JSP code, which in turn helps legitimize particular patterns of JSP use. For example, with an expressive enough JSP layer, JSTL's database tags can be used in a JSP-based controller without any meaningful loss of function when compared with servlets. And JSP pages, under JSP 2.0, can be used to create reusable tags. We had this feature-set in mind for JSTL 1.0 when we considered how to divide function among tags; by making each tag perform only one discrete task, we made them easily composable, like Unix command-line programs. Because of this, they can readily be arranged into patterns and then captured as new, higher-level custom tags. > >Shawn Bayern > >"JSTL in Action" http://www.jstlbook.com > > I need to buy this book sometime, so I'll know what my own EG generated. :) > :) :) :) Well, there are always the EG's archives, too! -- Shawn Bayern "JSTL in Action" http://www.jstlbook.com =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant FAQs on JSP/Servlets can be found at: http://archives.java.sun.com/jsp-interest.html http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.jsp http://www.jguru.com/faq/index.jsp http://www.jspinsider.com
