[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2603?page=c...
]
Landon Fuller commented on HHH-2603:
------------------------------------
Was the result of this discussion that:
- Developers should assume that in a future release, it will not be possible to
retrieve a JDBC Connection object at all?
or
- An API to retrieve the connection will be available in some other form?
The current JavaDoc notice is unclear on that point.
If there will be an alternative API to access a JDBC Connection, then I'm inclined to
attach a comment and @SupressWarnings attribute to my single use of connection(), and
replace the usage when the build breaks.
If the API is going away entirely, and access to an underlying JDBC connection will not be
available, then I need to write an alternative implementation.
Deprecate the Session.connection() method
-----------------------------------------
Key: HHH-2603
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2603
Project: Hibernate3
Issue Type: Deprecation
Components: core
Reporter: Steve Ebersole
Assignee: Steve Ebersole
Fix For: 3.2.4
Deprecate the Session.connection() method, in favor of a "JDBC work" API.
Schedule for removal in 4.0
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira