I have encountered a problem with Hibernate 3.3.1.GA and I tried to
override the version with 3.5.5-Final in my project pom-file, but it
seems that I have to build tapestry from source using the same Hibernate
version (see stack trace). If this is the case, I wonder if there are
many Tapestry users who need to maintain their own branch of Tapestry.
How do you deal with issues like this?
...
Caused by: java.lang.IncompatibleClassChangeError:
org/hibernate/cfg/ExtendedMappings
at
org.hibernate.cfg.AnnotationConfiguration.createExtendedMappings(AnnotationConfiguration.java:187)
at
org.hibernate.cfg.AnnotationConfiguration.addPackage(AnnotationConfiguration.java:177)
at
org.apache.tapestry5.internal.hibernate.PackageNameHibernateConfigurer.configure(PackageNameHibernateConfigurer.java:49)
at
org.apache.tapestry5.internal.hibernate.HibernateSessionSourceImpl.<init>(HibernateSessionSourceImpl.java:41)
at
org.apache.tapestry5.hibernate.HibernateCoreModule.buildHibernateSessionSource(HibernateCoreModule.java:123)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.tapestry5.ioc.internal.ServiceBuilderMethodInvoker.createObject(ServiceBuilderMethodInvoker.java:64)
...
Thanks,
Mats
