[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-2603) Deprecate the Session.connection() method

[Steve Ebersole (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=31992#action_31992 ] 

Steve Ebersole commented on HHH-2603:
-------------------------------------

Shawn, I am responding specifically to the questions that keep cropping up on this specific issue which invariable seem to discuss exactly this type of usage.

Its been discussed (and I thought you were involved in some of them) that yes there still needs to be an API for obtaining a 'child session' (specifically one utilizing the same JDBC connection).  This will happen before 4.0.  The rub, to me, is the already large number of overloaded SF.openSession() methods we have; that needs to be considered carefully.  But honestly I have not had time to think through the details of it; feel free to put some thought into it and start a discussion on the dev list.  (BTW Session.getSession(EntityMode) has a totally different purpose/intent)

> Deprecate the Session.connection() method
> -----------------------------------------
>
>                 Key: HHH-2603
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2603
>             Project: Hibernate Core
>          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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira