[
https://issues.apache.org/jira/browse/TAP5-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194227#comment-15194227
]
ASF subversion and git services commented on TAP5-2525:
-------------------------------------------------------
Commit 2869383aa77f11fdf1ef800ddd1eef9ba30acaae in tapestry-5's branch
refs/heads/master from kaosko
[ https://git-wip-us.apache.org/repos/asf?p=tapestry-5.git;h=2869383 ]
FIXED - TAP5-2525: Tapestry-Hibernate integration incompatible with
Hibernate 5.x
- apply a pull request by annorax <[email protected]> as a patch
(https://patch-diff.githubusercontent.com/raw/apache/tapestry-5/pull/2.patch)
- the patch makes it possible to use both Hibernate 4 & 5 with T5.4
- fix imports, compilation failures
- apply formatting
> Tapestry-Hibernate integration incompatible with Hibernate 5.x
> --------------------------------------------------------------
>
> Key: TAP5-2525
> URL: https://issues.apache.org/jira/browse/TAP5-2525
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-hibernate
> Affects Versions: 5.4
> Reporter: I D
> Assignee: Kalle Korhonen
>
> The following exception is thrown when attempting to start up tapestry with
> the latest stable version of Hibernate (5.0.6.Final):
> {code:java}
> java.lang.NoSuchMethodError:
> org.hibernate.cfg.Configuration.getClassMappings()Ljava/util/Iterator;
> at
> org.apache.tapestry5.hibernate.modules.HibernateModule.contributeValueEncoderSource(HibernateModule.java:95)
> ~[tapestry-hibernate-5.4.0.jar:na]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[na:1.8.0_60]
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> ~[na:1.8.0_60]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> ~[na:1.8.0_60]
> at java.lang.reflect.Method.invoke(Unknown Source) ~[na:1.8.0_60]
> at
> org.apache.tapestry5.ioc.internal.ContributionDefImpl.invokeMethod(ContributionDefImpl.java:125)
> ~[tapestry-ioc-5.4.0.jar:na]
> {code}
> That is due to the fact that getClassMappings() was removed from
> org.hibernate.cfg.Configuration in Hibernate 5.
> Luckily, it isn't really needed, and there is a backwards compatible way to
> do without it. I.e., tapestry can easily become compatible with Hibernate 5
> without breaking compatibility with Hibernate 3 and 4.
> I'll create a pull request on GitHub and link to it here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
