This looks subtle. What are you saving by doing it this way?
-A
On Mon, 8 Mar 1999, nicolas pujol wrote:
> 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".
