Jump to: navigation, search

EclipseLink/Examples/JPA/IntegrityChecker

< EclipseLink‎ | Examples‎ | JPA
Revision as of 11:54, 25 November 2009 by James.sutherland.oracle.com (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


How to validate the mappings against the database

By default EclipseLink assumes that the provided metadata matches the underlying database. This assumption is made to speed up application bootstrapping. During development however it is possible to enable validation of the mappings against the database using the IntegrityChecker. This how-to focuses on using the IntegrityChecker with EclipseLink JPA.


Enabling the IntegrityChecker

This must be done using a session customizer:

public static class EnableIntegrityChecker implements SessionCustomizer {
 
	public void customize(Session session) throws Exception {
		session.getIntegrityChecker().checkDatabase();	
		session.getIntegrityChecker().setShouldCatchExceptions(false);
	}
}

Configuring the SessionCustomizer

A session customizer can be configured in the persistence unit's properties in either XML or in a properties Map passed to Persistence.createEntityManagerFactory("unit-name", properties).

properties.put(PersistenceUnitProperties.SESSION_CUSTOMIZER, EnableIntegrityChecker.class.getName());