This is an attempt to raise design and higher level questions on the use of
JSP pages and JavaBeans.
I keep seeing people on this mailing list using all kind of convoluted
coding with their JSP pages, particularly in the context of holding session.
I would like to make a point. As far as I am concerned the beauty of JSP
rests almost exclusively in the BEAN tag or more recently the USEBEAN tag.
Apart from the that JSP is nothing more than a regular scripting language
like ASP or Javascript and LiveConnect.
I believe that as Java programmers we have to support the virtues of
OOP/OOD. The Bean tag should be used over extensive scripting within the
JSP. Using beans allows for easy maintenance of a page and more generally of
a site. In addition, it allows for Web development teams to delegate more
clearly their work into JavaBeans programmers (business logic) and Web
Designers (web presentation). It is important to note that the two have to
come together at some point. It is this "point of convergence" that needs to
be analyzed and studied extensively by Web architects.
Interestingly enough it appears that JSP and JavaBeans can work solely
without the need for servlets. In short, servlets as such are really
marginalized by JSP's. On the other hand, JSP pages are pre-servlets and are
compiled to servlets by the JSP engine after all. In my mind JSPs simply
facilitate the use and the coding of servlets.
Please send me your remarks.
Nicolas Pujol
Waterstone Consulting
===========================================================================
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".
