> > Problem:
> > JSP is becoming too complex.
> > The current vision as discussed emphasizes "model
> > 2".
>
> Agree - Model 1 should be the emphasized Model for two reasons:
> 1)Model 2 hinders bean interoperability. A bean written for Model
> 2 can only
> be used with its Model 2 servlet.
> 2) Model 2 is more difficult for newbies because you need to know how to
> write a servlet, how to dispatch or redirect, etc.
Although model two is poorly explained in the spec, it is neither difficult,
nor does it hinder bean interoperablity. You can pass *ANY* bean to a JSP
page. The utility of Model 2 is that you can use your existing beans to
create a dynamic web interface for your "legacy" system without writing new
business objects.
As for newbies creating semi-complex systems in JSP (w/o Servlets)...good
luck. Without model two, JSP is a project manager's worst nightmare.
Rob
===========================================================================
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".
