>
> > > 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.
Let me clarify.
1. Model 2 is poorly explained in the spec. This in itself is a
serious problem.
2. Model 2 is difficult:
a) Code must be scattered or crowbarred across servlets (who know
context), beans (who compute, and save session), and jsp (for
display). This is obviously more complex than jsp (for display)
and beans (from computation, display, and session handling).
b) Model 2 requires configuration of servlets, jsp, and beans. Each
of which have different means of configuration. Some of which
must touch several server config files. (that sucks)
>
> 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.
3. Ah you see the vision. The current system is too confusing for low
end users. This is exactly my point.
I would suggest:
a) newbee gets several "neat" beans.
b) newbee uses a graphic tool to layout his/her neat page
b) newbee configures the "neat" beans in a central <!-- #include
c) newbee runs jsp calling neat beans.
-end of story-
I do not suggest: (the current system)
a) newbee gets several "neat" beans
b) newbee talks with sysadmin about how to configure
the servlet components of his/her beans
c) newbee edits his/her components in an ascii editor because
jsp neads beans/servlets/jsp code to work and that is pretty
tough for most graphic html packages to muster.
d) newbee must understand how to configure servlets, jsp, and
serialize beans.
e) newbee must understand how to fetch session from servlets and
use easy/nifty jsp session management if he/she wants any
session passed info between beans/servlets.
f) lots of other really silly/useless/frightening steps.
g)
h)
i)
.
Hope this helps make JSP better,
-jason
>
> 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".
>
===========================================================================
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".
