looks like very logical and clear model, but see:
you submit your forms to servelt. (I also like
one servlet per application, just more easy to
maintain). So your logic (application logic) is
supported by servlet. What in that case the added
value from JSP-beans to web-application ?
Yes, we have some business rules implementation,
localized within some java classes. But we can use these
classes from servlet. I am feeling myself some trouble
to split beans/servlets during own "jsp-projects" for the
clients. Looks like in the most cases it is still "servlet-
projects" because any attempt to add some dynamic/behavior
to your JSP pages directly means java-coding within the page
what is not a good.
-----------------------------------------
* JSP page contains an input form. The values
are pre-filled-in from a session bean that contains
application default values the first time through,
or the most recent inputs after a validation error
(see below for more info).
* Form submit goes to a servlet (I tend to
use a single servlet per app, others like
a servlet per input form).
* Servlet dispatches to the business logic
responsible for processing this form.
ColdJava: java server side programming
http://coldjava.hypermart.net
____________________________________________________________________
Get your own FREE, personal Netscape WebMail account today at
http://webmail.netscape.com.
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
