The JSP to JavaBean would be the efficient way to do it
And also for the login check also it is better to go in for a bean
and eliminate all the direct data accesses from the page
Hope it helps
Regards
Sanjay
-----Original Message-----
From: Mahesh Chhatlani [mailto:[EMAIL PROTECTED]]
Sent: 17 January 2001 17:34
To: [EMAIL PROTECTED]
Subject: JSP to database communication
Hi,
Which is the "suggested" way to access the database, say for an intermediate
query that throws out about 100 rows.
(1) JSP to db directly on a JSP page
(2) JSP to JavaBean (where the bean has all the db access)
(c) JSP to Servlet (where the Servlet accesses the db)
For quick login checks, etc I use the 1st method.
What about queries that throw out more than 1000 rows? Which method is the
"suggested" one?
Thanks.
--mahesh
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST
DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
