EDIT

Hi Ben,

Yes probably you right. I didn't really go into the PersistentTermInitializerTest problem but tried it within eclipse with the new override.properties and it worked whereas in maven it doesn't

Caused by: java.lang.ClassCastException: org.hibernate.collection.PersistentSet cannot be cast to java.util.SortedSet

  at eu.etaxonomy.cdm.model.common.OrderedTermVocabulary.addTerm(OrderedTermVocabulary.java:154)


  at eu.etaxonomy.cdm.model.common.OrderedTermVocabulary.addTerm(OrderedTermVocabulary.java:1)


  at eu.etaxonomy.cdm.database.PersistentTermInitializer.firstPass(PersistentTermInitializer.java:141)


  at eu.etaxonomy.cdm.database.PersistentTermInitializer.initialize(PersistentTermInitializer.java:87)

I will leave the test as @Ignored for now.

Cheers,

Andreas

----Ursprüngliche Nachricht-----

Von: Ben Clark B.Clark@kew.org

Gesendet: Donnerstag, 5. Februar 2009 11:07

An: 'dev-cdmlib@mnhn.fr'

Betreff: RE: [dev-cdmlib] I want to commit some major changes to cdmlib term loading, please could you confirm that this is ok?

Hi Andreas,

For PersistentTermInitializerTest I had to create a new override.properties because for this test it looks like > we need term initializing. Or do I think the wrong way here?

I'm not sure what to do about PersistentTermInitializerTest, really, as running it side-by-side with the other tests (which use testing term initializer) results in some issues. I think disabling it using override.properties simply checks against the terms initialized by TestingTermInitializer, not actually testing the PersistentTermInitializer at all.

I just @Ignore -ed it, not a perfect solution, but the whole term initialization scenario is quite complex and I couldn't think of a better idea. Running the other tests properly is more of a priority, I think.

Cheers,

   Ben