[hibernate-issues] [Hibernate-JIRA] Commented: (HSHARDS-42) Investigate why ShardedSession extends org.hibernate.classic.Session instead of org.hibernate.Session

[Max Rydahl Andersen (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HSHARDS-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_27760 ] 

Max Rydahl Andersen commented on HSHARDS-42:
--------------------------------------------

it's so you will work seamlessly with an existing hibernate session ;)

classic.Session were introduced to allow users to still use the Hibernate2 "normal" ways of doing queries etc.

I don't think skipping that can become relevant before H4

> Investigate why ShardedSession extends org.hibernate.classic.Session instead of org.hibernate.Session
> -----------------------------------------------------------------------------------------------------
>
>                 Key: HSHARDS-42
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSHARDS-42
>             Project: Hibernate Shards
>          Issue Type: Task
>          Components: engine
>            Reporter: Max Ross
>            Assignee: Max Ross
>             Fix For: 3.0.0
>
>
> Just like the description says.  Is there a reason for this?  If not we can switch and then get rid of all the impls of deprecated methods.

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