I also object to processRequest() on the grounds that it makes a "JSP-aware"
beans. Having coded up such beans, I found that all processRequest() usually
did was redirect to a public method (so that the bean can be used outside of
JSP).
It's a cleaner design to have JSP manipulate beans with the well understood
getX, setX, and method invocation.
Also, what is a JSP design tool suppose to do when a JSP-aware bean is
instantiated? Should it fake out a HttpServletRequest and invoke
processRequest()? Will bean developers have to ensure that their bean
operates correctly when processRequest is not called?
Tuyen Tran
----- Original Message -----
From: Hans Bergsten <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 05, 1999 9:59 PM
Subject: Re: The importance of processRequest()...
> The problem with processRequest in Beans is that by adding it, the Bean
> is no longer a Bean, it's a "JSP Bean". This may be mostly academic, but
> JSP 1.0 lays the groundwork for a much better alternative namely the
> Tag Extension framework. The Tag Extension framework will let you define
> your own tags that by definition are "active". You could for instance
> develop a
>
===========================================================================
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".
