Vaughn, (or is your first name Wine??)
I can't agree with you more. WHY would anyone want to write 2
pages/servlets to do the job of one? Its hard enough keeping code in
synch when doing multi-tier stuff, so having 4 'layers' (JSP+Servlets/
BEANS/CORBA/DB) just seams like a waste of time to me.
In ASP, you have very little choice but to write all your code in
VBScript/JScript, as writing an ActiveX in VB/Delphi (C++ is a joke
for rapid dev) is, well, silly, 'cos you have to restart the server
every
time!!! With JSP, its so easy to write beans to do all the dirty work,
and leave the presentation up to the JSP. Model 2 just seams a very
round-about way to do it.
But thats just IMO, naturally :) Each to their own.
Nic.
Wine Vaughn wrote:
>
> I've been monitoring this list server for several weeks now, and several
> people have commented that they like using Model 2. (There are two JSP
> approaches mentioned in JSP spec 0.92. They are refereed to as Model 1 and
> Model 2.)
>
> Why? What advantages does Model 2 have over Model 1?
>
> I've used Model 1 in several scenarios, and I cannot see what advantage
> Model 2 would provide. The only thing that comes to mind is Model 2
> separates the logic a little bit more. However, I prefer to have the bean
> do the processing with processRequest, instead of dividing the work between
> a servlet and bean....
>
> Comments?
>
> Vaughn Wine
>
> ===========================================================================
> 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".
