Using AcrossHibernateJpaModule

The AcrossHibernateJpaModule builds a JPA EntityManager for a Persistence Unit with the same name, using Hibernate as the implementation engine. Other modules can configure mappings in the EntityManager by adding them to the HibernatePackage that the AcrossHibernateJpaModule handles.

The AcrossHibernateJpaModule serves as an alternative for using the spring-boot-starter-data-jpa in a multi-module application.

Using an @AcrossApplication with across-autoconfigure and spring-boot-starter-data-jpa, you might have JPA enabled in your application module. The latter however does not easily allow shared Across modules to attach to the same EntityManager.

In an Across application module, using AcrossHibernateJpaModule should not necessarily require any changes. If you simply add AcrossHibernateJpaModule to your application configuration, it will transparently replace the spring-boot-starter-data-jpa functionality:

Most of the default behaviour can be controlled using the module settings. If you do not want to use the default entity scan or Spring Data repository scan, you should treat the application module as if it is a shared module and register your entities manually.

AcrossHibernateJpaModule also makes it easier to work with multiple entity managers in a single application.

In a simple application the developer probably has to do nothing to make use of the EntityManager provided by the AcrossHibernateJpaModule. If you want to use the EntityManager in a shared module, there’s a couple of steps involved:

AcrossHibernateJpaModule always creates a PlatformTransactionManager and enables transaction management support in all modules bootstrapping later. When having multiple JPA modules in a single application, you will have multiple transaction managers and you will have to specify which one to use.