In the lib area of the seam download there used to be a hibernate.jar.
This is no longer present in 2.2.0.CR1.
I now see various hiberante jars. (core, entitymanager, validator etc.).
Which ones should I use and should they be added to the EAR (application.xml)
Should they be added to the Jar and be added to the build path (BuildPath - Add To Build Path).
I have to have hibernate-validator.jar added to Jar build path as I call it and I have a compile problem in the IDE without it!.
InvalidValue invalidValues = Validators.instance().getValidator(MailingListEntry.class).getPotentialInvalidValues("email", email);
I notice 2 things...
1. I can launch with JUST hibernate-validator.jar in the jar onto Jboss-4.2.1.GA and all still works but I think that Jboss may actually ship with hibernate so its picking up an old version... In startup I see:
19:18:51,565 INFO [PersistenceUnitDeployment] Starting persistence unit persistence.units:ear=Sec.ear,jar=SecEJB.jar,unitName=secDatabase 19:18:51,596 INFO [Version] Hibernate EntityManager 3.2.1.GA 19:18:51,627 INFO [Version] Hibernate Annotations 3.2.1.GA 19:18:51,643 INFO [Environment] Hibernate 3.2.4.sp1 19:18:51,643 INFO [Environment] hibernate.properties not found
2. Looking round examples (useful for building an Ear and cracking it to see what should be deployed) I found that the wiki example has hiberante3.jar.
Welcome to red belt java.
Now all I got to do is really understand it!
I am still confused by this!
The jars need to be in the build path. If you are using 4.2.1.GA you will also have to update the application servers hibernate version or bundle the new libraries in the ear. Note that the new version of hibernate has some other dependencies that will also have to be added.