Is there any way to control the hibernate.archive.autodetection property?
I have two persistence units in my persistence.xml, and I'd love to instruct the first to autodetect classes only from package.1.orm and the second from package.2.orm.

Is it possible within one application with two separate persistence units without specifying the classes explicitly?

I'm using the latest:
Hibernate Core 3.2.6
Hibernate Annotations 3.3.0
Hibernate EntityManager 3.3.1

If it's not possible, should I care actually? What I'm doing is a DB migration, and I'm moving objects from one DB to another one, hence two persistence units (both providers are org.hibernate.ejb.HibernatePersistence, and I don't think this will change).

Thanks for any tips,

I think you'll have to list your classes explicitely unless you manage to split your entities into 2 separate jars

I recently had the same problem, and I found that I had to do this:
- create 2 different persistent units in persistence.xml
- disable autodetection for Hibernate
- in each of these persistent units I enlisted the classes which where to map to a unit (with the <class> element
- in each of these persistent units I put a something like[i]<mapping-file>META-INF/orm_xxxx.xml</mapping-file>, to differentiate the externalized queries to be used be each persistent unit.

So, if you don't want to put the list of mapped classes into persistence.xml, you can put them into an "orm" file.

The most important experience for me was:
- you cannot rely on the "schema" property on the annotated class
- therefore you must prevent Hibernate validation using reflection on the annotated classes (it ignores the schema values!)
- you have to force Hibernate to do validation using the descriptions in persistence.xml and orm.xml.

I also think, there is some mismatch between Hibernate's DDL schema creation tool and Hibernate's runtime validation process; the first one differentiates on the schema values in the annotations, the latter doesn't do this.

Carlo

I've managed to split them into two separate jar's - good idea, and now using the <jar-file> property in persitence.xml I've exactly what I've wanted, thanks for your help

How do you declare the jars ??
A)


B)


?

Can you provide an example of the persistence.xml file? I'm trying to use two persistence-units and can't get Hibernate to not scan both jars twice...