RE: beans and JSPs and stuff...

["Stone, Brad V (TC)" <bvstone@xxxxxxxxxxxxxx>]

> But such changes can only be made in CGI through programming 
> the host side.  In a JSP environment, most web presence 
> changes can be made without touching the host logic.  With 
> the CGI approach, every change in the presentation, from 
> trivial to extensive, must be done through the CGI programs.

No they don't!  Not if you're using stylesheets and SSI.  Then you can just
change HTML files just as you would JSPs.  Move the SSI include around on
the page and it moves the dynamic content.  Change the stylesheet to change
the look. 

> 
> The only way around this is to write a CGI program that in 
> essence reads a specialized HTML page and plugs in your 
> dynamic content wherever it's needed.

No it's not Joe.  I know I show my ignorance with Java and OO often, but
this statement tells me that you probably haven't done quite as much CGI
programming as I.  But then again, that's your "argument" for JSPs.  You
don't need to.  But, still, my point stays.  

> 
> And that's... a JSP!
> 
> Also, the speed of a JSP is exactly the same as that for a 
> servlet, since a JSP is a servlet.  There is an initial 
> compile time for a new JSP, or when the JVM is first fired 
> up.  That can be reduced by preloading JSPs as necessary.

JSPs are compiled by the server before they are run, unless that has
suddenly changed and I missed the RFC.  I would also think that there is
more room for typos causing runtime syntax errors to say the least.

Brad
+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---