Implements org.hibernate.jpa.spi.JpaCompliance.isGlobalGeneratorScopeEnabled.

Doc from org.hibernate.jpa.spi.JpaCompliance.isGlobalGeneratorScopeEnabled.

Should the the scope of javax.persistence.TableGenerator#name() and javax.persistence.SequenceGenerator#name() be considered globally or locally defined?

Returns:boolean

true indicates the generator name scope is considered global.

Annotations

@Override

Implements org.hibernate.jpa.spi.JpaCompliance.isJpaCacheComplianceEnabled.

Doc from org.hibernate.jpa.spi.JpaCompliance.isJpaCacheComplianceEnabled.

Should Hibernate comply with all aspects of caching as defined by JPA? Or can it deviate to perform things it believes will be "better"?

Returns:boolean

true says to act the spec-defined way.

Annotations

@Override

Implements org.hibernate.jpa.spi.JpaCompliance.isJpaClosedComplianceEnabled.

Doc from org.hibernate.jpa.spi.JpaCompliance.isJpaClosedComplianceEnabled.

JPA defines specific exceptions on specific methods when called on javax.persistence.EntityManager and javax.persistence.EntityManagerFactory when those objects have been closed. This setting controls whether the spec defined behavior or Hibernate's behavior will be used. If enabled Hibernate will operate in the JPA specified way throwing exceptions when the spec says it should with regard to close checking

Returns:boolean

true indicates to behave in the spec-defined way

Annotations

@Override

Implements org.hibernate.jpa.spi.JpaCompliance.isJpaListComplianceEnabled.

Doc from org.hibernate.jpa.spi.JpaCompliance.isJpaListComplianceEnabled.

Controls how Hibernate interprets a mapped List without an "order columns" specified. Historically Hibernate defines this as a "bag", which is a concept JPA does not have. If enabled, Hibernate will recognize this condition as defining a org.hibernate.collection.internal.PersistentList, otherwise Hibernate will treat is as a org.hibernate.collection.internal.PersistentBag

Returns:boolean

true indicates to behave in the spec-defined way, interpreting the mapping as a "list", rather than a "bag"

Annotations

@Override

Implements org.hibernate.jpa.spi.JpaCompliance.isJpaProxyComplianceEnabled.

Doc from org.hibernate.jpa.spi.JpaCompliance.isJpaProxyComplianceEnabled.

JPA spec says that an javax.persistence.EntityNotFoundException should be thrown when accessing an entity Proxy which does not have an associated table row in the database. Traditionally, Hibernate does not initialize an entity Proxy when accessing its identifier since we already know the identifier value, hence we can save a database roundtrip. If enabled Hibernate will initialize the entity Proxy even when accessing its identifier.

Returns:boolean

true indicates to behave in the spec-defined way

Annotations

@Override

Implements org.hibernate.jpa.spi.JpaCompliance.isJpaQueryComplianceEnabled.

Doc from org.hibernate.jpa.spi.JpaCompliance.isJpaQueryComplianceEnabled.

Controls whether Hibernate's handling of JPA's javax.persistence.Query (JPQL, Criteria and native-query) should strictly follow the JPA spec. This includes both in terms of parsing or translating a query as well as calls to the javax.persistence.Query methods throwing spec defined exceptions where as Hibernate might not. Deviations result in an exception if enabled

Returns:boolean

true indicates to behave in the spec-defined way

Annotations

@Override

Implements org.hibernate.jpa.spi.JpaCompliance.isJpaTransactionComplianceEnabled.

Doc from org.hibernate.jpa.spi.JpaCompliance.isJpaTransactionComplianceEnabled.

Indicates that Hibernate's Transaction should behave as defined by the spec for JPA's javax.persistence.EntityTransaction since it extends the JPA one.

Returns:boolean

true indicates to behave in the spec-defined way

Annotations

@Override