[ http://issues.apache.org/jira/browse/BEEHIVE-1168?page=comments#action_12460369 ] Drew Varner commented on BEEHIVE-1168: --------------------------------------
I think part of this should be some sort of contract on the getConnection() method. We allow the user to pull a Connection out, but don't tell him/her what can be done with it. As I understand it, a Connection obtained will be closed at the end of a NetUI action. The user could place it in the user's Session for use in Webapp. The Control would close the Connection after the Pageflow's action and the Connection in Session would be useless for future calls. The getConnection() method Javadocs need to establish some sort of contract on what the user can expect after the Connection is pulled. The documentation would warn that the connection will be closed when the Context releases the Control. It's up to the user to determine which Context their control is in and when it will call release. > Update the JDBC system control documentation to include a section on resource > management > ---------------------------------------------------------------------------------------- > > Key: BEEHIVE-1168 > URL: http://issues.apache.org/jira/browse/BEEHIVE-1168 > Project: Beehive > Issue Type: Improvement > Components: Documentation > Affects Versions: V.Next > Reporter: Chad Schoettger > Priority: Minor > > Add a new section to the JDBC system control doc describing how the JDBC > control manages JDBC connections to a database. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
