Re: beans and JSPs and stuff...

The primary reason is that JSPs can be maintained by non-programmers.  If you 
design your widgets properly (widgets being the classes that are invoked by the 
JSP), then even a non-programmer can place them on the screen.  For example, my 
file maintenance JSPs have basically two working lines: instantiate the file 
maintenance widget bean and then display it.  However, as the requirements get 
more complex (for example, placing different fields in different places on the 
screen), the JSP designer can get a little fancier.  He needs to know the names 
of the fields, but that's about it.  My widgets also allow the designer to 
attach HTML characteristics directly to the widget, such as colors and borders 
and the like.  This is clearly in the province of the JSP designer, not the 
programmer.  To require a change in the program and a recompilation every time 
I want to change the background color of a field description is very 
counterproductive.  Instead, the JSP designer can use any HTML editor 
(including Notepad!).  The cycle is fast: edit the JSP, change the color ID, 
save it and refresh the browser.  And anybody with a text editor can do that - 
they don't even need a Java compiler on their machine.

---------- Original Message ----------------------------------
From: "Stone, Brad V (TC)" <bvstone@taylorcorp.com>
Reply-To: JAVA400-L@midrange.com
Date: Tue, 27 Feb 2001 07:17:39 -0600

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.

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