Hello,

We have a database with over 300 tables we would like to test through unit-like tests. Therefore I would like to instantly create an in memory database (HSQL) with only the few classes/tables that are tested in that particular test.

The problem is that all mappings are related so that the only thing I can do is to include all classes in the hibernate.cfg.xml. Else exceptions like these occur:



Is it possible to modify the configuration of mappings-loading (as is done by the SessionFactory) so that referenced unmapped classes are ignored?

In production this is something you do not want to happen, but from within tests it would be a nice feature.

Greetings,
Erwin

Let me explain why I need this.

Our application consists of two separate domains. Let's say Domain A and Domain B. Domain A depends on Domain B.

Given this example, Domain B is testable. With an in memory database (we use HSQL) and providing only the classes to map within the tests, a sort of Unit tests are created.

Domain A is much less isolated, because of the dependency on Domain B. Setting up all classes to map takes very long and is not needed for the tests to be done.

I really would like the SessionFactory to only warn if an unmapped class is referenced by a certain mapping.

Is that possible, or should I patch the SessionFactory for this?

Erwin