[
https://issues.apache.org/jira/browse/TORQUE-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Fox closed TORQUE-197.
-----------------------------
Resolution: Won't Fix
hm, the method getConnection() is also there.... which makes more sense because
the Torque instance keeps all the connection pools. I did not see this when
creating the issue.
Setting resolution to wontfix and closing issue.
> deprecate the method Torque.closeConnection()
> ---------------------------------------------
>
> Key: TORQUE-197
> URL: https://issues.apache.org/jira/browse/TORQUE-197
> Project: Torque
> Issue Type: Sub-task
> Components: Runtime
> Reporter: Thomas Fox
>
> All other connection handling methods are in Transaction. With pluggable
> transaction management as described in the super task, it makes no sense to
> have connection closing elsewhere.
> The method should be removed in Torque 4.1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscr...@db.apache.org
For additional commands, e-mail: torque-dev-h...@db.apache.org
