Le vendredi 12 août 2011 à 15:18 +0100, Sanne Grinovero a écrit :
Hi Cyrille,
5.0.0.FINAL was just released last week, and unfortunately introduced
a last minute API change which broke compatibility with OGM/Alpha2.
OGM master works fine now as it was a trivial fix, and I've deployed
an updated SNAPSHOT version, please try that one!
Not sure why it looked like to boot in your case.. you should have
seen a stacktrace at startup mentioning that Infinispan couldn't be
started,
please check your logs too.
Thanks Sanne,
Infinispan appears to boot. When configuring a GUI to talk to the app, I
can see both nodes talking to each other, and no log messages to the
contrary seem to happen.
Just tried with hibernate-ogm as such:
<version>3.0.0-SNAPSHOT</version>
Kept Infinispan as 5.0.0.FINAL, but saw the same on 5.1.0-SNAPSHOT
Now I get a failure to load; apparently, something else changed:
java.lang.NoSuchMethodError:
org.infinispan.config.InfinispanConfiguration.newInfinispanConfiguration(Ljava/lang/String;Ljava/lang/String;Lorg/infinispan/config/ConfigurationBeanVisitor;Ljava/lang/ClassLoader;)Lorg/infinispan/config/InfinispanConfiguration;
at
org.hibernate.ogm.datastore.infinispan.impl.CacheManagerServiceProvider.createCustomCacheManager(CacheManagerServiceProvider.java:126)
at
org.hibernate.ogm.datastore.infinispan.impl.CacheManagerServiceProvider.start(CacheManagerServiceProvider.java:80)
at
org.hibernate.ogm.metadata.GridMetadataManager.sessionFactoryCreated(GridMetadataManager.java:55)
at
org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:478)
at
org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1872)
at
org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:906)
at
org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:57)
at
org.hibernate.ogm.jpa.HibernateOgmPersistence.createEntityManagerFactory(HibernateOgmPersistence.java:99)
at
javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:63)
I'll clear the m2 cache tomorrow & try again, and if that fails I guess
I'll have to hit the SCM :)
-- Cyrille