| Modifier and Type | Field and Description |
|---|---|
| private boolean | |
| private boolean | |
| private final boolean | |
| private boolean | |
| private boolean | |
| private boolean | |
| private boolean |
| Access | Constructor and Description |
|---|---|
| public |
| cachingCompliance | back to summary |
|---|---|
| private boolean cachingCompliance | |
| closedCompliance | back to summary |
|---|---|
| private boolean closedCompliance | |
| globalGeneratorNameScopeCompliance | back to summary |
|---|---|
| private final boolean globalGeneratorNameScopeCompliance | |
| listCompliance | back to summary |
|---|---|
| private boolean listCompliance | |
| proxyCompliance | back to summary |
|---|---|
| private boolean proxyCompliance | |
| queryCompliance | back to summary |
|---|---|
| private boolean queryCompliance | |
| transactionCompliance | back to summary |
|---|---|
| private boolean transactionCompliance | |
| MutableJpaComplianceImpl | back to summary |
|---|---|
public MutableJpaComplianceImpl(Map<K, V> configurationSettings, boolean jpaByDefault)
| |
| immutableCopy | back to summary |
|---|---|
| public JpaCompliance immutableCopy() Implements org.
| |
| isGlobalGeneratorScopeEnabled | back to summary |
|---|---|
| public boolean isGlobalGeneratorScopeEnabled() Implements org. Doc from org. Should the the scope of
| |
| isJpaCacheComplianceEnabled | back to summary |
|---|---|
| public boolean isJpaCacheComplianceEnabled() Implements org. Doc from org. Should Hibernate comply with all aspects of caching as defined by JPA? Or can it deviate to perform things it believes will be "better"?
| |
| isJpaClosedComplianceEnabled | back to summary |
|---|---|
| public boolean isJpaClosedComplianceEnabled() Implements org. Doc from org. JPA defines specific exceptions on specific methods when called on
| |
| isJpaListComplianceEnabled | back to summary |
|---|---|
| public boolean isJpaListComplianceEnabled() Implements org. Doc from org. 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
| |
| isJpaProxyComplianceEnabled | back to summary |
|---|---|
| public boolean isJpaProxyComplianceEnabled() Implements org. Doc from org. JPA spec says that an
| |
| isJpaQueryComplianceEnabled | back to summary |
|---|---|
| public boolean isJpaQueryComplianceEnabled() Implements org. Doc from org. Controls whether Hibernate's handling of JPA's
| |
| isJpaTransactionComplianceEnabled | back to summary |
|---|---|
| public boolean isJpaTransactionComplianceEnabled() Implements org. Doc from org. Indicates that Hibernate's
| |
| setCachingCompliance | back to summary |
|---|---|
| public void setCachingCompliance(boolean cachingCompliance) Implements org. | |
| setClosedCompliance | back to summary |
|---|---|
| public void setClosedCompliance(boolean closedCompliance) Implements org. | |
| setListCompliance | back to summary |
|---|---|
| public void setListCompliance(boolean listCompliance) Implements org. | |
| setProxyCompliance | back to summary |
|---|---|
| public void setProxyCompliance(boolean proxyCompliance) Implements org. | |
| setQueryCompliance | back to summary |
|---|---|
| public void setQueryCompliance(boolean queryCompliance) Implements org. | |
| setTransactionCompliance | back to summary |
|---|---|
| public void setTransactionCompliance(boolean transactionCompliance) Implements org. | |