In the short while I have been using JSP, I have found the following to be the biggest point.
I can now, more cleanly, seperate the code form the presentation.  I have used servlets
extensively, and have swore by them, but I hated trying to have the HTML packed
up in some long out.println() method.  When ever *any* HTML changed, I had to go in
and recompile.  This isn't too bad when you are the only one doing everything, but
when web authors manage the pages, and a developer manages the logic classes,
JSP really provides a bridge that allows great *working-togetherness*.  They can concentrate
on their own talents and leave the other part to the one it belongs to.
 

==================================================================
James M. Birchfield                               646 Howards Loop
Software Engineer                                    Annapolis, MD
[EMAIL PROTECTED]                               (410) 897-5994
                  http://www.proteus-technologies.com
==================================================================

-----Original Message-----
From: A mailing list about Java Server Pages specification and reference [mailto:[EMAIL PROTECTED]]On Behalf Of Swapnil Gupta
Sent: Saturday, November 06, 1999 1:34 AM
To: [EMAIL PROTECTED]
Subject: In what ways does JSP score over Servlets ?

Hello Frenz,
                   I have gone through quite a bit of literature and information on JSPs and Servlets.
I do not find very convincing as to how JSPs score any significant advantage over Servlets. I am aware  and understand the more common points where JSP does well like easy maintanence and development and also some built in tag based support for easy interaction with EJB. Besides these are there any significant gains in going for JSP/Servlets rather than Servlets.
 
Thanks,
 
Swapnil.

Reply via email to