This week's book giveaway is in the OCMJEA forum. We're giving away four copies of OCM Java EE 6 Enterprise Architect Exam Guide and have Paul Allen & Joseph Bambara on-line! See this thread for details.
Need some advice on this. I have recently inherited a web application with unbelievably bad design(rather without any design at all ) . One of the problems is JSP's calling methods which open up a connection, create a statement, and then, believe it or not, return the result set to the JSP. The original programmer merrily forgot about closing the statement. Now, of course, the best approach would be to factor away all JDBC code into java beans etc., but there are constraints on time and resources available. One possible solution I am considering is - In each JSP page, after it is finished with the result-set, call resultSet.close() and resultSet.getStatement().close(). One thing to note here is that the original connection used to create the statement would have been returned to the pool, and possibly new Statement objects created from it. Ugly as it is, but do you think this would work? Anything that I am overlooking here! thanks
The future is here. It's just not evenly distributed yet. - William Gibson
Consultant @ Xebia. Sonny GillTweets