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

[Dilip Dalton (JIRA)]

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

Dilip Dalton commented on HHH-2603:
-----------------------------------

Removing this method without an alternative to getting a JDBC connection will prevent us from upgrading to 4.0.

The product we work is a huge enterprise level J2EE software with more than a million lines of java code. The code has been developed on for more than a decade and we have different persistent mechanisms (JDBC, direct hibernate, Spring with hibernate) that need to work together. The common transaction semantics is achieved by passing the JDBC connection from the hibernate session to the legacy part of the code that needs to work with JDBC.

It is not possible to rewrite all the code using hibernate. So please let us know if an alternative method to get the JDBC connection from hibernate session will be provided.


> 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