Documentation
Liferay provides a rich store of resources and knowledge to help our community better use and work with our technology.
JPA
Set this property to none to disable the JPA validation. Some application servers have the validation JARs in the global class path which causes conflicts with Hibernate. See LPS-22453 for more information.
javax.persistence.validation.mode=none
Input a list of comma delimited JPA configurations.
jpa.configs=\
META-INF/mail-orm.xml,\
META-INF/portal-orm.xml
Set the name of the JPA provider.
Examples:
jpa.provider=eclipselink
jpa.provider=hibernate
jpa.provider=openjpa
jpa.provider=toplink
Specify provider specific properties prefixed with jpa.provider.property.
*Examples:
jpa.provider.property.eclipselink.allow-zero-id=true
jpa.provider.property.eclipselink.logging.level=FINEST
jpa.provider.property.eclipselink.logging.timestamp=true
The LoadTimeWeaver interface is a Spring class that allows JPA ClassTransformer instances to be plugged in a specific manner depending on the environment.
Not all JPA providers require a JVM agent (Hibernate is an example). If your provider does not require an agent or you have other alternatives (such as applying enhancements at build time through a custom compiler or an Ant task), then the loadtime weaver should not be used.
Examples:
jpa.load.time.weaver=org.springframework.instrument.classloading.ReflectiveLoadTimeWeaver
jpa.load.time.weaver=org.springframework.instrument.classloading.glassfish.GlassFishLoadTimeWeaver
jpa.load.time.weaver=org.springframework.instrument.classloading.oc4j.OC4JLoadTimeWeaver
jpa.load.time.weaver=org.springframework.instrument.classloading.weblogic.WebLogicLoadTimeWeaver
Specify a specific database platform setting if the JPA provider is not able to detect the database platform.
Valid values for the Hibernate and OpenJPA providers are: DB2, DERBY, HSQL, INFORMIX, MYSQL, ORACLE, POSTGRESQL, SQL_SERVER, and SYBASE.
Valid values for the EclipseLink provider are: org.eclipse.persistence.platform.database.DB2MainframePlatform, org.eclipse.persistence.platform.database.DB2Platform, org.eclipse.persistence.platform.database.DerbyPlatform, org.eclipse.persistence.platform.database.HSQLPlatform, org.eclipse.persistence.platform.database.InformixPlatform, org.eclipse.persistence.platform.database.MySQLPlatform, org.eclipse.persistence.platform.database.OraclePlatform, org.eclipse.persistence.platform.database.PostgreSQLPlatform, org.eclipse.persistence.platform.database.SQLServerPlatform, or org.eclipse.persistence.platform.database.SybasePlatform.
Check with JPA provider's documentation for details and all possible values.
jpa.database.platform=
Liferay will automatically detect the database type by initializing DBUtil. You can override the value here if needed. Expected values are: db2, derby, firebird, hypersonic, informix, ingres, interbase, jdatastore, mysql, oracle, postgresql, sap, sqlserver, and sybase.
jpa.database.type=