Printlns in servlets are a terrible way of doing things, worse than embedded
html in perl scripts, in my book.
Even if your the only person that'll ever need to change the code (which I
doubt) you'll be kicking yourself when all you have is ftp access and you
quickly need to change the alignment of a heading.
You should always separate, as much as possible (which is generally all the
time) your business logic from you display/presentation logic.
/c - someone who has worked on sites that were start with that attitude
----------
>The only reason I use JSP is because I need to enable
>our customers to modify the presentation. If you don't need
>to expose the presentation logic to another person,
>your Web page designer or customers, there is no real
>compelling reason to use JSP. println in servlets is not so
>bad after all.
>
>TK
>
>-----Original Message-----
>From: LEGA, Laura <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
>Date: Wednesday, June 02, 1999 3:46 AM
>Subject: JSP versus servlets
>
>
>>Hello everybody out there!
>>
>>I'm trying to understand if JSP can help me in doing what I have to do
>>better than servlets.
>>For example: a page with a <SELECT> tag whose values are the result of a
>>dynamic query to a DataBase.
>>
>>Does it worth that I try to understand all the mess of JSP or should I
>>simply use a servlet and a thousand of println(<various tags>)?
>>
>>If anyone could help that would be great and save me a lot of time.
>>
>>Thank you in advance,
>>
>>Laura
>>
===========================================================================
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".
