Interface SessionFactoryBuilder

    • Method Detail

      • applyValidatorFactory

        SessionFactoryBuilder applyValidatorFactory​(Object validatorFactory)
        Apply a Bean Validation ValidatorFactory to the SessionFactory being built. NOTE : De-typed to avoid hard dependency on Bean Validation jar at runtime.
        Parameters:
        validatorFactory - The Bean Validation ValidatorFactory to use
        Returns:
        this, for method chaining
      • applyBeanManager

        SessionFactoryBuilder applyBeanManager​(Object beanManager)
        Apply a CDI BeanManager to the SessionFactory being built. NOTE : De-typed to avoid hard dependency on CDI jar at runtime.
        Parameters:
        beanManager - The CDI BeanManager to use
        Returns:
        this, for method chaining
      • applyAutoClosing

        SessionFactoryBuilder applyAutoClosing​(boolean enabled)
        Applies whether Sessions should be automatically closed at the end of the transaction.
        Parameters:
        enabled - true indicates they should be auto-closed; false indicates not.
        Returns:
        this, for method chaining
        See Also:
        AvailableSettings.AUTO_CLOSE_SESSION
      • applyAutoFlushing

        SessionFactoryBuilder applyAutoFlushing​(boolean enabled)
        Applies whether Sessions should be automatically flushed at the end of the transaction.
        Parameters:
        enabled - true indicates they should be auto-flushed; false indicates not.
        Returns:
        this, for method chaining
        See Also:
        AvailableSettings.FLUSH_BEFORE_COMPLETION
      • applyStatisticsSupport

        SessionFactoryBuilder applyStatisticsSupport​(boolean enabled)
        Applies whether statistics gathering is enabled.
        Parameters:
        enabled - true indicates that statistics gathering should be enabled; false indicates not.
        Returns:
        this, for method chaining
        See Also:
        AvailableSettings.GENERATE_STATISTICS
      • addSessionFactoryObservers

        SessionFactoryBuilder addSessionFactoryObservers​(SessionFactoryObserver... observers)
        Specifies one or more observers to be applied to the SessionFactory. Can be called multiple times to add additional observers.
        Parameters:
        observers - The observers to add
        Returns:
        this, for method chaining
      • addEntityNameResolver

        SessionFactoryBuilder addEntityNameResolver​(EntityNameResolver... entityNameResolvers)
        Specifies one or more entity name resolvers to be applied to the SessionFactory (see the EntityNameResolver contract for more information.. Can be called multiple times to add additional resolvers..
        Parameters:
        entityNameResolvers - The entityNameResolvers to add
        Returns:
        this, for method chaining
      • applyEntityNotFoundDelegate

        SessionFactoryBuilder applyEntityNotFoundDelegate​(EntityNotFoundDelegate entityNotFoundDelegate)
        Names the EntityNotFoundDelegate to be applied to the SessionFactory. EntityNotFoundDelegate is a strategy that accounts for different exceptions thrown between Hibernate and JPA when an entity cannot be found.
        Parameters:
        entityNotFoundDelegate - The delegate/strategy to use.
        Returns:
        this, for method chaining
      • applyIdentifierRollbackSupport

        SessionFactoryBuilder applyIdentifierRollbackSupport​(boolean enabled)
        Should generated identifiers be "unset" on entities during a rollback?
        Parameters:
        enabled - true indicates identifiers should be unset; false indicates not.
        Returns:
        this, for method chaining
        See Also:
        AvailableSettings.USE_IDENTIFIER_ROLLBACK
      • applyNullabilityChecking

        SessionFactoryBuilder applyNullabilityChecking​(boolean enabled)
        Should attributes using columns marked as not-null be checked (by Hibernate) for nullness?
        Parameters:
        enabled - true indicates that Hibernate should perform nullness checking; false indicates it should not.
        Returns:
        this, for method chaining
        See Also:
        AvailableSettings.CHECK_NULLABILITY
      • applyLazyInitializationOutsideTransaction

        SessionFactoryBuilder applyLazyInitializationOutsideTransaction​(boolean enabled)
        Should the application be allowed to initialize uninitialized lazy state outside the bounds of a transaction?
        Parameters:
        enabled - true indicates initialization outside the transaction should be allowed; false indicates it should not.
        Returns:
        this, for method chaining
        See Also:
        AvailableSettings.ENABLE_LAZY_LOAD_NO_TRANS
      • applyDefaultBatchFetchSize

        SessionFactoryBuilder applyDefaultBatchFetchSize​(int size)
        Allows specifying a default batch-fetch size for all entities and collections which do not otherwise specify a batch-fetch size.
        Parameters:
        size - The size to use for batch fetching for entities/collections which do not specify an explicit batch fetch size.
        Returns:
        this, for method chaining
        See Also:
        AvailableSettings.DEFAULT_BATCH_FETCH_SIZE
      • applyMaximumFetchDepth

        SessionFactoryBuilder applyMaximumFetchDepth​(int depth)
        Apply a limit to the depth Hibernate will use for outer joins. Note that this is different than an overall limit on the number of joins...
        Parameters:
        depth - The depth for limiting joins.
        Returns:
        this, for method chaining
        See Also:
        AvailableSettings.MAX_FETCH_DEPTH
      • applyDefaultNullPrecedence

        SessionFactoryBuilder applyDefaultNullPrecedence​(NullPrecedence nullPrecedence)
        Apply a null precedence (NULLS FIRST, NULLS LAST) to be applied order-by clauses rendered into SQL queries.
        Parameters:
        nullPrecedence - The default null precedence to use.
        Returns:
        this, for method chaining
        See Also:
        AvailableSettings.DEFAULT_NULL_ORDERING
      • applyOrderingOfInserts

        SessionFactoryBuilder applyOrderingOfInserts​(boolean enabled)
        Apply whether ordering of inserts should be enabled. This allows more efficient SQL generation via the use of batching for the inserts; the cost is that the determination of the ordering is far more inefficient than not ordering.
        Parameters:
        enabled - true indicates that ordering should be enabled; false indicates not
        Returns:
        this, for method chaining
        See Also:
        AvailableSettings.ORDER_INSERTS
      • applyOrderingOfUpdates

        SessionFactoryBuilder applyOrderingOfUpdates​(boolean enabled)
        Apply whether ordering of updates should be enabled. This allows more efficient SQL generation via the use of batching for the updates; the cost is that the determination of the ordering is far more inefficient than not ordering.
        Parameters:
        enabled - true indicates that ordering should be enabled; false indicates not
        Returns:
        this, for method chaining
        See Also:
        AvailableSettings.ORDER_UPDATES
      • applyMultiTenancy

        SessionFactoryBuilder applyMultiTenancy​(boolean enabled)
        Apply the form of multi-tenancy used by the application
        Parameters:
        enabled - True if multi-tenancy in use.
        Returns:
        this, for method chaining
      • applyJtaTrackingByThread

        SessionFactoryBuilder applyJtaTrackingByThread​(boolean enabled)
        If using the built-in Hibernate JTA-based TransactionCoordinator/Builder, should it track JTA transactions by thread in an attempt to detect timeouts?
        Parameters:
        enabled - true indicates we should track by thread; false indicates not
        Returns:
        this, for method chaining
        See Also:
        AvailableSettings.JTA_TRACK_BY_THREAD
      • applyPreferUserTransactions

        SessionFactoryBuilder applyPreferUserTransactions​(boolean preferUserTransactions)
        If using the built-in Hibernate JTA-based TransactionCoordinator/Builder, should it prefer to use UserTransaction over Transaction?
        Parameters:
        preferUserTransactions - true indicates we should prefer UserTransaction; false indicates we should prefer Transaction
        Returns:
        this, for method chaining
        See Also:
        AvailableSettings.PREFER_USER_TRANSACTION
      • applyNamedQueryCheckingOnStartup

        SessionFactoryBuilder applyNamedQueryCheckingOnStartup​(boolean enabled)
        Should named queries be checked on startup?
        Parameters:
        enabled - true indicates that they should; false indicates they should not.
        Returns:
        this, for method chaining
        See Also:
        AvailableSettings.QUERY_STARTUP_CHECKING
      • applySecondLevelCacheSupport

        SessionFactoryBuilder applySecondLevelCacheSupport​(boolean enabled)
        Should second level caching support be enabled?
        Parameters:
        enabled - true indicates we should enable the use of second level caching; false indicates we should disable the use of second level caching.
        Returns:
        this, for method chaining
        See Also:
        AvailableSettings.USE_SECOND_LEVEL_CACHE
      • applyQueryCacheSupport

        SessionFactoryBuilder applyQueryCacheSupport​(boolean enabled)
        Should second level query caching support be enabled?
        Parameters:
        enabled - true indicates we should enable the use of second level query caching; false indicates we should disable the use of second level query caching.
        Returns:
        this, for method chaining
        See Also:
        AvailableSettings.USE_QUERY_CACHE
      • applyMinimalPutsForCaching

        SessionFactoryBuilder applyMinimalPutsForCaching​(boolean enabled)
        By default, Hibernate will always just push data into the cache without first checking if that data already exists. For some caches (mainly distributed caches) this can have a major adverse performance impact. For these caches, it is best to enable this "minimal puts" feature.

        Cache integrations also report whether "minimal puts" should be enabled by default. So its is very rare that users need to set this, generally speaking.

        Parameters:
        enabled - true indicates Hibernate should first check whether data exists and only push to the cache if it does not already exist. false indicates to perform the default behavior.
        Returns:
        this, for method chaining
        See Also:
        AvailableSettings.USE_MINIMAL_PUTS, RegionFactory.isMinimalPutsEnabledByDefault()
      • applyStructuredCacheEntries

        SessionFactoryBuilder applyStructuredCacheEntries​(boolean enabled)
        By default, Hibernate stores data in the cache in its own optimized format. However, that format is impossible to "read" if browsing the cache. The use of "structured" cache entries allows the cached data to be read.
        Parameters:
        enabled - true indicates that structured cache entries (human readable) should be used; false indicates that the native entry structure should be used.
        Returns:
        this, for method chaining
        See Also:
        AvailableSettings.USE_STRUCTURED_CACHE
      • applyDirectReferenceCaching

        SessionFactoryBuilder applyDirectReferenceCaching​(boolean enabled)
        Generally, Hibernate will extract the information from an entity and put that extracted information into the second-level cache. This is by far the safest way to second-level cache persistent data. However, there are some cases where it is safe to cache the entity instance directly. This setting controls whether that is used in those cases.
        Parameters:
        enabled - true indicates that applicable entities will be stored into the second-level cache directly by reference; false indicates that all entities will be stored via the extraction approach.
        Returns:
        this, for method chaining
        See Also:
        AvailableSettings.USE_DIRECT_REFERENCE_CACHE_ENTRIES
      • applyAutomaticEvictionOfCollectionCaches

        SessionFactoryBuilder applyAutomaticEvictionOfCollectionCaches​(boolean enabled)
        When using bi-directional many-to-one associations and caching the one-to-many side it is expected that both sides of the association are managed (actually that is true of all bi-directional associations). However, in this case, if the user forgets to manage the one-to-many side stale data can be left in the second-level cache.

        Warning: enabling this will have a performance impact. Hence why it is disabled by default (for good citizens) and is an opt-in setting.

        Parameters:
        enabled - true indicates that these collection caches should be evicted automatically.
        Returns:
        this, for method chaining
        See Also:
        AvailableSettings.AUTO_EVICT_COLLECTION_CACHE
      • applyJdbcBatchSize

        SessionFactoryBuilder applyJdbcBatchSize​(int size)
        Specifies the maximum number of statements to batch together in a JDBC batch for insert, update and delete operations. A non-zero number enables batching, but really only a number greater than zero will have any effect. If used, a number great than 5 is suggested.
        Parameters:
        size - The batch size to use.
        Returns:
        this, for method chaining
        See Also:
        AvailableSettings.STATEMENT_BATCH_SIZE
      • applyJdbcBatchingForVersionedEntities

        SessionFactoryBuilder applyJdbcBatchingForVersionedEntities​(boolean enabled)
        This setting controls whether versioned entities will be included in JDBC batching. The reason being that some JDBC drivers have a problems returning "accurate" update counts from batch statements. This is setting is false by default.
        Parameters:
        enabled - The batch size to use.
        Returns:
        this, for method chaining
        See Also:
        AvailableSettings.BATCH_VERSIONED_DATA
      • applyScrollableResultsSupport

        SessionFactoryBuilder applyScrollableResultsSupport​(boolean enabled)
        Should scrollable results be supported in queries? We ask the JDBC driver whether it supports scrollable result sets as the default for this setting, but some drivers do not accurately report this via DatabaseMetaData. Also, needed if user is supplying connections (and so no Connection is available when we bootstrap).
        Parameters:
        enabled - true to enable this support, false to disable it
        Returns:
        this, for method chaining
        See Also:
        AvailableSettings.USE_SCROLLABLE_RESULTSET
      • applySqlComments

        SessionFactoryBuilder applySqlComments​(boolean enabled)
        Should Hibernate apply comments to SQL it generates?
        Parameters:
        enabled - true indicates comments should be applied; false indicates not.
        Returns:
        this, for method chaining
        See Also:
        AvailableSettings.USE_SQL_COMMENTS
      • applyCollectionsInDefaultFetchGroup

        SessionFactoryBuilder applyCollectionsInDefaultFetchGroup​(boolean enabled)
        Should collections be included in the default fetch group when bytecode enhancement is used?
        Parameters:
        enabled - true collections should be included
        Returns:
        this, for method chaining
      • allowOutOfTransactionUpdateOperations

        SessionFactoryBuilder allowOutOfTransactionUpdateOperations​(boolean allow)
      • enableReleaseResourcesOnCloseEnabled

        SessionFactoryBuilder enableReleaseResourcesOnCloseEnabled​(boolean enable)
        Should resources held by EntityManager instance be released immediately on close?

        The other option is to release them as part of an after-transaction callback.

      • unwrap

        <T extends SessionFactoryBuilder> T unwrap​(Class<T> type)
        Allows unwrapping this builder as another, more specific type.
        Returns:
        The unwrapped builder.
      • build

        SessionFactory build()
        After all options have been set, build the SessionFactory.
        Returns:
        The built SessionFactory.