[jira] [Commented] (TAP5-1922) Upgrade Hibernate dependency to latest, Hibernate 4.1.2.Final

["Kalle Korhonen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TAP5-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263720#comment-13263720 ] 

Kalle Korhonen commented on TAP5-1922:
--------------------------------------

5.4 trunk is already using Hibernate 4.1.1.Final. T5.3.x is using Hibernate 3.6 dependency and unfortunately, you need to recompile tapestry-hibernate if you want to use it together with Hibernate 4.1, see below (Jochen Frey reported this earlier on the dev mailing list). Suddenly bumping up the Hibernate version from 3.6.x to 4.1.x in a patch fix release might create more problems than it solves. As part of this issue, I'm upgrading T5.4 trunk to Hibernate 4.1.2 and closing the issue.

On Thu, Mar 22, 2012 at 11:23 AM, Jochen Frey <jo...@jochenfrey.com> wrote:
> Hey Kalle, thanks for the quick response.
>
> I think I found the reason why it's not working for me (and I am surprised what you're describing could have worked for you at all).  By way of a unit test I tried your approach (adding the <dependency> for Hibernate 4.1.1), and for me it fails with a
>
>        Caused by: java.lang.NoSuchMethodError: org.hibernate.SessionFactory.openSession()Lorg/hibernate/classic/Session;
>
> Since then I have found the reason for that, which this that SessionFactory.openSession() in:
> - Hibernate 4.1 returns org.hibernate.Session
> - Hibernate 3.6 returns org.hibernate.classic.Session.

                
> Upgrade Hibernate dependency to latest, Hibernate 4.1.2.Final
> -------------------------------------------------------------
>
>                 Key: TAP5-1922
>                 URL: https://issues.apache.org/jira/browse/TAP5-1922
>             Project: Tapestry 5
>          Issue Type: Task
>          Components: tapestry-hibernate
>    Affects Versions: 5.3.3
>            Reporter: Felix Scheffer
>            Priority: Minor
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira