Re: In what ways does JSP score over Servlets ?

[Richard Friedman]

1. Looping. How have you handled looping in your template language.  Not that this is impossible, but you probably have created your own mini-language.  Also, can you handle loops within loops? 2. Performance. The act of playing templates I could imagine be more costly than JSP style coding.  Not including whatever caching mechanism you might have, there is still processing of the template logic.  I assume that everytime you hit a placeholder, you have some action being triggered.  Your engine is doing all the work, why not have the templates themselves drive the process by converting them to java and let them run themselves.  Yes, I know, this is JSP.  ( IMHO, JSP was the next logical step from template-style engines. ) 3. Templates separate things too cleanly! In your template approach, imagine you wanted to change the appearnce of a single cell within a table based on some value.  This is not business logic, but presentation logic, hence having the ability to code within your template based on what the template is about to display, is a clean separation.  Also, for more detail on separating code see sun's application programming model (http://java.sun.com/j2ee).  I do not agree with everything in there but it is a good start. just my 2 cents. -Rich. -----Original Message----- From: Husted, Robert [mailto:[EMAIL PROTECTED]] Sent: Monday, November 08, 1999 2:44 PM To: [EMAIL PROTECTED] Subject: Re: In what ways does JSP score over Servlets ?     At Qwest we are using templates... HTML files with placeholders for data ${MY_PLACEHOLDER}.  We store the template in memory and then insert the data into the template and display it to the user.  The advantage is that our HTML code doesn't appear in the Servlet.  In addition, our Java code doesn't appear in the template... so we've cleanly separated the Java code from the HTML.     What is the advantage of using a JSP over a Servlet that uses templates? As far as I can tell, there is no advantage... we've actually done a better job of separating code and presentation logic using templates.  Can someone give me a concrete example of when JSPs might be better than a Servlet that employs templates?     Thanks,     - Robert  =)  -----Original Message----- From: Steve Wamsley [mailto:[EMAIL PROTECTED]] Sent: Saturday, November 06, 1999 12:54 PM To: [EMAIL PROTECTED] Subject: Re: In what ways does JSP score over Servlets ? -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 1. JSP's are really servlets when comes right down to it. 2. Do you really want to create a large-scale browser-based application composing all the HTML in out.println() calls? Steve Wamsley http://home.earthlink.net/~sswamsley <http://home.earthlink.net/~sswamsley> - ----- Original Message ----- From: Swapnil Gupta To: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Sent: Saturday, November 06, 1999 12:33 AM 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. -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 6.5.1 for non-commercial use < http://www.pgp.com <http://www.pgp.com> > iQA/AwUBOCSHS5aPN/z+dlkyEQJy+wCgixBL1l4Z29AqycOql58X/XgHYVcAmweG UZgBH1r0H8xBRNTLL3U8LhN2 =qJdz -----END PGP SIGNATURE----- =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". FAQs on JSP can be found at:  http://java.sun.com/products/jsp/faq.html  http://www.esperanto.org.nz/jsp/jspfaq.html