G
Greg Smith
I guess it comes down to how you design the application. I'm not trying
i hear you... it does seem to me that we're forgetting the lessons
learned over the last 30 years of software engineering. to make
multiple pages when one (plus a little logic) will do, increases the
cost of maintenance. and maintenance is the most expensive phase of
the life cycle. but that may be a different thread.
thanks for your help.
to dodge anything here, merely noting that if you have complex logic to
execute then it properly belongs in the servlet, not the JSP.
As I mentioned previously, JSP is all about presentation. About the only
logic I generally incorporate involves checking for roles or errors and
displaying accordingly.
Remember that the servlet has the choice as to which page to forward to;
don't try to make a single page suffice for all situations when you can
instead have multiple processing paths. Such an approach would obviate
the need for complex logic processing at the page level, don't you think?
i hear you... it does seem to me that we're forgetting the lessons
learned over the last 30 years of software engineering. to make
multiple pages when one (plus a little logic) will do, increases the
cost of maintenance. and maintenance is the most expensive phase of
the life cycle. but that may be a different thread.
thanks for your help.