Check for valid configuration for LocalContainerEntityManagerFactoryBean

This rule flags the Spring beans in the Spring configuration file with the class: org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean when the bean is not configured with the property entityManagerFactoryInterface .

When using JPA, there is a conflict in the Spring EntityManagerFactory that requires configuring the entityManagerFactoryInterface property. This issue and its resolution are documented on the Spring web site.

Set the value for entityManagerFactoryInterface to javax.persistence.EntityManagerFactory . You can also set the entityManagerFactoryInterface property to a provider specific value. However, note that between JPA 2.0 and JPA 2.1, the default JPA provider for WebSphere traditional and Liberty was switched from OpenJPA to EclipseLink. It is recommended to use the spec provided value, javax.persistence.EntityManagerFactory , for easier migration.

The automated fix will add the the new entityManagerFactoryInterface property to the bean with the value javax.persistence.EntityManagerFactory . If the user wants to use any of the other possible values, then the user will need to do that manually, to the Spring configuration file. The new entry will be added as the last child element in the bean definition.

The bean in the following example Spring configuration file would be flagged because there is no entityManagerFactoryInterface property configured in the bean.

<bean id="myEMF" class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean">
<property name="jpaVendorAdapter">
<bean class="org.springframework.orm.jpa.vendor.OpenJpaVendorAdapter" />
</property>
<property name="jpaProperties">
<props>
<prop key="openjpa.Log">DefaultLevel=TRACE</prop>
</props>
</property>
</bean>

For additional information, see: