I completely agree with John here. I know that the whole "event processing"
mechanism (.jsa stuff) is being "figured out" for JSP 1.1, and processRequest()
belongs in that family of events, but there are some problems that are
*much* easier to solve with the processRequest() machinery as it stands
in JSP 0.92. The "guarded pages" example John presents is a good one, and
I have a couple of other beans that require the request to initialize
their state. I can get around with with a common include file or scriptlet,
but it's less than ideal.
So I vote for the reinstatement of processRequest() as it currently stands,
even though it will be subject to change in JSP 1.1.
On Wed, 5 May 1999 13:14:19 -0400, John Langley <[EMAIL PROTECTED]> wrote:
>and a 'use case' in the form of "guarded pages"
>a.k.a. required login.
>
>I noticed in the 1.0 preliminary spec. that the "processRequest
>machinery" is listed under the heading of "Postponed for Evaluation
>in Future Releases". I would like to voice a strong positive statement
>in favor of including the processRequest() machinery (as soon as
>possible). Here's why...
>
--
Eric Lunt
mailto:[EMAIL PROTECTED] Ph: 312-642-9050 Fax: 312-642-9051
Burning Door, LLC (http://www.burningdoor.com)
"Helping our clients build effective web applications"
===========================================================================
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".
