Servlet/jsp/jdbc best approach

Question

Hello guys
Which is the best approach when developing servlet/jsp/jdbc? I will take an
example:
I have index-page, page2 and page 3.
When the user writes www.mydomain.com then the page index.jsp checks if the
user is coming from the servlet, like this:
<%
if(request.getAttribute("getPageTitle")==null){
%>
<jsp:forward page="/Index" />
<%
else{
%>
<%@ include file="/include/header.jsp" %>
content for index.jsp
<%@ include file="/include/footer.jsp" %>
<%
%>
On the other hand, the Index class has this init()
public void init(ServletConfig config) throws ServletException {
super.init(config);
con = DatabaseConf.getConnection();
DatabaseConf is a class that handles all the operations related to the
database.
Index.class has also the doGet-method like this:
request.setAttribute ("getPageTitle", "AnyTilte");
getServletConfig().getServletContext().getRequestDispatcher("/index.jsp").forward(request,
response);
Does it looks ok so long?
Now, I have other pages, page2 and page3 (in fact I have mych more than just
these, but this is only an example)
pages.jsp works as index.jsp. It makes a check
<%
if(request.getAttribute("getPageTitle")==null){
%>
if not satisfied than it redirect to
<jsp:forward page="/Page2" />
My concern, however, is about databasemanagement. Even the Page.class has an
init-method that looks exactly like the one in Index.class, e.g.
public void init(ServletConfig config) throws ServletException {
super.init(config);
con = DatabaseConf.getConnection();
In conclusion, Im starting jdbc-connection for every class-file that
initiates. Is this a good approach? What I would like is a solution to
initiate the database only one time, when the server starts. Not everytime,
the first time a specially class-file will be called. I know, this will
happens only one time for a file for the server's lifetime. But Im afraid
this is not a good way to work.
Regards
email2us

Answer 1

Hello guys
Which is the best approach when developing
servlet/jsp/jdbc? I will take an
example:
I have index-page, page2 and page 3.
When the user writes www.mydomain.com then the page
index.jsp checks if the
user is coming from the servlet, like this:
<%
if(request.getAttribute("getPageTitle")==null){
%>
<jsp:forward page="/Index" />
<%
else{
%>
<%@ include file="/include/header.jsp" %>
content for index.jsp
<%@ include file="/include/footer.jsp" %>
<%
%>
On the other hand, the Index class has this init()
public void init(ServletConfig config) throws
ServletException {
super.init(config);
con = DatabaseConf.getConnection();
DatabaseConf is a class that handles all the
operations related to the
database.
Index.class has also the doGet-method like this:
request.setAttribute ("getPageTitle", "AnyTilte");
getServletConfig().getServletContext().getRequestDispa
tcher("/index.jsp").forward(request,
response);
Does it looks ok so long?
Now, I have other pages, page2 and page3 (in fact I
have mych more than just
these, but this is only an example)
pages.jsp works as index.jsp. It makes a check
<%
if(request.getAttribute("getPageTitle")==null){
%>
if not satisfied than it redirect to
<jsp:forward page="/Page2" />
My concern, however, is about databasemanagement.
Even the Page.class has an
init-method that looks exactly like the one in
Index.class, e.g.
public void init(ServletConfig config) throws
ServletException {
super.init(config);
con = DatabaseConf.getConnection();
Please use the code formatting tags when posting actual code.
In conclusion, Im starting jdbc-connection for every
class-file that
initiates. Is this a good approach? You normally do not want your Servlet to initiate (which I take to mean 'startup') a database. The two can run independently. The place to initiate a database is in your operating system's startup scripts.
What I would like
is a solution to
initiate the database only one time, when the server
starts. Not everytime,
the first time a specially class-file will be called.If you are talking about java.sql.Connection, you generally do not want to have a single connection for your entire application. Each thread should use its own connection, or transaction management/logical unit of work will be problematic, at best. You can use a connection pool to improve performance. However, from a caller's perspective, they are receiving a new connection each time.
I know, this will
happens only one time for a file for the server's
lifetime. But Im afraid
this is not a good way to work.
Regards
email2us- Saish