Kevin HaleBoyes wrote:
>
> Thanks for your help. I ended up doing something similar to this. I had
> intended to package the request info into the Order beans and then forward
> to a servlet to do some database checking. So I reversed the order a bit
> and POST to the servlet, have it construct the beans, attach them to the
> session, do validation, then forward to a JSP to respond to the user.
That's an even better solution than using a custom action for this type of
processing.
> Seems to work well and since I'm still learning tablib support in JSP I'm not
> as comfortable with that kind of solution.
I wasn't sure how comfortable you where with servlets and the MVC model,
so that's why I suggested a pure JSP solution while still getting the
Java code out of the page and into a real Java class (the custom action).
Another reason for using a custom action example was to show that they
are not so complicated to develop as some people make them out to be;
a custom action is basically a glorified bean with a couple of extra methods
called by the web container to make them do what they need to do :-)
Hans
--
Hans Bergsten [EMAIL PROTECTED]
Gefion Software http://www.gefionsoftware.com
Author of JavaServer Pages (O'Reilly), http://TheJSPBook.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://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
