[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-5981) Clarify Session.disconnect() and Session.reconnect() behavior

[Steve Ebersole (JIRA)]

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

Steve Ebersole commented on HHH-5981:
-------------------------------------

Actually I decided to continue to allow calls to disconnect() even if the connection was not user supplied.  This is still useful in some conversation scenarios.

> Clarify Session.disconnect() and Session.reconnect() behavior
> -------------------------------------------------------------
>
>                 Key: HHH-5981
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5981
>             Project: Hibernate Core
>          Issue Type: Remove Feature
>          Components: core
>            Reporter: Steve Ebersole
>            Assignee: Steve Ebersole
>             Fix For: 4.0.0.Alpha1
>
>          Time Spent: 3h 26m
>  Remaining Estimate: 0h
>
> Specific changes:
> # disallow disconnect() except in cases where the user supplied the connection to the session
> # disallow disconnect() if there is an existing, active transaction associated with the Session.
> # remove reconnect() (it has been deprecated for some time now)
> # disallow reconnect(Connection) unless the user initially supplied the connection to the Session

-- 
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