I would suggest that you handle all your database transactions and/or data
aquisition in servlets, and then let JSP's display that data. It is a lot
easier to code your data aquisition in a servlet than in a JSP, and it also
improves the speed of your display.
William J Ortiz
Information Analyst Associate
XGAF - Metered Supplies
Phone: (716) 427-6892
e-mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
e
-----Original Message-----
From: Chandra, Debmalya (CAP, RAIL)
[mailto:[EMAIL PROTECTED]]
Sent: Friday, September 29, 2000 11:02 AM
To: [EMAIL PROTECTED]
Subject: [SERVLET-INTEREST] Servlet or JSP
Hi friends,
I have a "HTML ready" page. I mean someone has already done the screen in
HTML. The controls in the page are like : textarea(s), command buttons,
comboboxes. My job is to populate the screen using SQL server DB. I might
have to design similar "HTML ready" screens which are all interlinked (i.e.
they would call and pass information among themselves). There are some front
end validations too.
Could you suggest if I should go for JSP under this situation or servlets.
In other words, what kind of technique should one go for, so that
development time is quickest (and easy too), given that the developer has
some background in Java, but more in ASP.
TIA.
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
