On Tue, 15 Oct 2002, Wolfgang Röckelein wrote: > I see that, too. JSP/JSTL/EL is DO and not OO. However, the decision > remains how to deal with user input submissions which usually require > some action (if it is not merely a change in a display format etc., > but e.g. a new entry, a changed order state, etc.). One approach to > this problem is of course the struts way, but I think the JSP/JSTL/EL > community should have an answer to this (we have already the modifying > SQL statements in JSTL..). One answer could be the execution of a > (bean) method...One valid answer could also be, JSP/JSTL per se has no > business in this area, do this with custom tags or struts or...
You can think of the "lightweight" JSP 2.0 / JSTL 1.1 model -- that is, the use of these technologies even without a supporting framework like Struts -- as encouraging users to execute logic in servlets and restrict JSP pages to simple display. When the JSP pages need to make a more complex decision, there are a number of ways to provide them with more advanced capabilities: - tag libraries written in Java - tag libraries written in JSP, perhaps using scriptlets - functions, provided through a tag library The goal, under this model, is for such tag libraries to complement JSTL for a specific application's needs. -- Shawn Bayern "JSTL in Action" http://www.jstlbook.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
