beans and JSPs and stuff...

I had to rename this thread, Mr. Bartell is probably on the cover of the
Enquierer by now.. ;)

> 
>    html page --calls--> a servlet
>    servlet accesses parms from the request
>            builds object(s) [i.e. beans]
>            binds objects to request, session, etc
>    servlet --forwards request--> jsp
>    jsp contains html with tags to access beans
>    jsp --sends--> document to browser
> 

This makes sense.  But why not have a servlet output HTML.  Why JSP?  In my
experience with using both JSPs tend to run a bit slower (because of the
background compile).  Instead, I'd rather write a small servlet to output
the HTML.

6 of one?  Or is JSP really an advantage?  I understand from one point you
have programmers writing servlets and web programmers writing JSP/HTML, but
you still need to know something about JSP to do it, it's not just HTML.  I
don't think any web application I've written is simple enough to have
someone who just knows HTML write the "presentation" layer.  Especially if I
want the application to dynamic, not just "rebranded" by copying everything
and changing the JSPs.  

We do have one company that does that and they're admitting now that it
wasn't the best choice.  OTOH, The appilcations I wrote I make them so they
just use a green screen to reformat the screen, reface it, etc.  Much less
to take care of.

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
+---