This is almost exactly what I do. For example:
<USEBEAN NAME="save" TYPE=foo.bar.SaveTheWhales LIFESPAN=page>
<SETFROMREQUEST BEANPROPERTY="*">
</USEBEAN>
<%
getServletContext().getResourceDispatcher("/SaveTheWhalesResponse.jsp").forw
ard(request, response);
%>
Scott
-----Original Message-----
From: Nicolas Pujol <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Friday, March 05, 1999 4:45 PM
Subject: Non-visual JSP
>I was thinking about the idea of a non visual JSP as a means to avoid ever
>writing servlets. A JSP page is a servlet after all. Can you think of any
>drawbacks in using this approach.
>
>For example, let's say I have a form on a page. When I "submit the page"
>(via a POST) I would be pointing to a another JSP page:
>
><form action="handle.jsp" method="post">
>........
></form>
>
>handle.jsp would then handle POST by the <@% method %> directive,
>instantiate a database bean and pass data to the bean via introspection and
>then simply redirect itself to another page via
>response.sendRedirect("index.html"). Thus handle.jsp would never be
>displayed but would be doing work anyway.
>
>How is that different than using directly a servlet to handle the POST and
>redirecting to another page????
>
>Nicolas
>
>===========================================================================
>To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
>of the message "signoff JSP-INTEREST". For general help, send email to
>[EMAIL PROTECTED] and include in the body of the message "help".
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
