| Modifier and Type | Method and Description |
|---|---|
| public MetadataBuilder | Returns: this, for method chainingThe access-type to use as default. accessType)Specify the second-level access-type to be used by default for entities and collections that define second-level caching, but do not specify a granular access-type. |
| public MetadataBuilder | Returns: this, for method chainingThe ArchiveDescriptorFactory to use. factory)Specify a particular ArchiveDescriptorFactory instance to use in scanning. |
| public MetadataBuilder | Returns: this for method chainingThe definition definition)
Deprecated
(since 5.3) AttributeConverterDefinition forces early
access to the AttributeConverter instance which precludes the
possibility to resolve the converter from CDI, etc. Instead use
one of:
*
Adds an AttributeConverter by an AttributeConverterDefinition
applyAttributeConverter(Class)
* applyAttributeConverter(Class, boolean)
* applyAttributeConverter(AttributeConverter)
* applyAttributeConverter(AttributeConverter, boolean)
|
| public MetadataBuilder | Returns: this for method chainingThe AttributeConverter class. attributeConverterClass)Adds an AttributeConverter by its Class. |
| public MetadataBuilder | Returns: this for method chainingThe AttributeConverter class. attributeConverterClass, boolean Should the AttributeConverter be auto applied to property types as specified
by its "entity attribute" parameterized type? autoApply)Adds an AttributeConverter by its Class plus a boolean indicating whether to auto apply it. |
| public MetadataBuilder | Returns: this for method chainingThe AttributeConverter instance. attributeConverter)Adds an AttributeConverter instance. |
| public MetadataBuilder | Returns: this for method chainingThe AttributeConverter instance. attributeConverter, boolean Should the AttributeConverter be auto applied to property types as specified
by its "entity attribute" parameterized type? autoApply)Adds an AttributeConverter instance, explicitly indicating whether to auto-apply. |
| public MetadataBuilder | |
| public MetadataBuilder | Returns: this, for method chainingThe type addition or override. type)Specify an additional or overridden basic type mapping. |
| public MetadataBuilder | Returns: this, for method chainingThe type addition or override. type, String... The keys under which to register the basic type. keys)Specify an additional or overridden basic type mapping supplying specific registration keys. |
| public MetadataBuilder | Returns: this, for method chainingThe custom type type, String... The keys under which to register the custom type. keys)Register an additional or overridden custom type mapping. |
| public MetadataBuilder | Returns: this, for method chainingThe composite custom type type, String... The keys under which to register the composite custom type. keys)Register an additional or overridden composite custom type mapping. |
| public MetadataBuilder | Returns: this, for method chainingThe cache region definition to apply cacheRegionDefinition)Apply a CacheRegionDefinition to be applied to an entity, collection or query while building the Metadata object. |
| public MetadataBuilder | |
| public MetadataBuilder | Returns: this, for method chainingThe implicit catalog name implicitCatalogName)Specify the implicit catalog name to apply to any unqualified database names. |
| public MetadataBuilder | Returns: this, for method chainingThe ImplicitNamingStrategy to apply namingStrategy)Specify the ImplicitNamingStrategy to use in building the Metadata. |
| public MetadataBuilder | Returns: this, for method chainingThe implicit schema name implicitSchemaName)Specify the implicit schema name to apply to any unqualified database names. |
| public MetadataBuilder | Returns: this, for method chainingThe Jandex index to use. jandexView)Allows specifying a specific Jandex index to use for reading annotation information. |
| public MetadataBuilder | Returns: this, for method chainingThe PhysicalNamingStrategy to apply namingStrategy)Specify the PhysicalNamingStrategy to use in building the Metadata. |
| public MetadataBuilder | Returns: this, for method chainingThe environment for scanning scanEnvironment)Consider this temporary as discussed on |
| public MetadataBuilder | Returns: this, for method chainingThe scanner to use. scanner)Specify a particular Scanner instance to use. |
| public MetadataBuilder | Returns: this, for method chainingThe scan options. scanOptions)Specify the options to be used in performing scanning. |
| public MetadataBuilder | Returns: this, for method chainingThe cache mode. cacheMode)Specify the second-level cache mode to be used. |
| public MetadataBuilder | Returns: this for method chainingThe types, in the order they should be processed sourceTypes)Apply a specific ordering to the processing of sources. |
| public MetadataBuilder | |
| public MetadataBuilder | Returns: this, for method chainingClassLoader for use during building the Metadata tempClassLoader)Apply a ClassLoader for use while building the Metadata. |
| public MetadataBuilder | Returns: this, for method chainingThe contributor to apply typeContributor)Apply an explicit TypeContributor (implicit application via ServiceLoader will still happen too) |
| public Metadata | |
| public MetadataBuilder | Returns: this, for method chainingShould processing (not ignoring) explicit discriminators be
enabled? enabled)Should we process or ignore explicitly defined discriminators in the case of joined-subclasses. |
| public MetadataBuilder | Returns: this, for method chainingtrue says to use nationalized variants; false
says to use the non-nationalized variants.Should nationalized variants of character data be used in the database types? |
| public MetadataBuilder | Returns: this, for method chainingShould we implicitly create discriminator for joined
inheritance if one is not explicitly mentioned? enabled)Similarly to |
| public MetadataBuilder | Returns: this, for method chainingtrue indicates we will force the discriminator into the select;
false indicates we will not.For entities which do not explicitly say, should we force discriminators into SQL selects? |
| public MetadataBuilder | Returns: this, for method chainingtrue to enable; false to disable; don't call for
default.Should we enable support for the "new" (since 3.2) identifier generator mappings for handling: |
| public <T extends MetadataBuilder> T |
| applyAccessType | back to summary |
|---|---|
| public MetadataBuilder applyAccessType(AccessType accessType) Specify the second-level access-type to be used by default for entities and collections that define second-level caching, but do not specify a granular access-type.
Its default is defined by the
| |
| applyArchiveDescriptorFactory | back to summary |
|---|---|
| public MetadataBuilder applyArchiveDescriptorFactory(ArchiveDescriptorFactory factory) Specify a particular ArchiveDescriptorFactory instance to use in scanning.
Its default is defined by the
| |
| applyAttributeConverter | back to summary |
|---|---|
| public MetadataBuilder applyAttributeConverter(AttributeConverterDefinition definition)
Deprecated (since 5.3) AttributeConverterDefinition forces early
access to the AttributeConverter instance which precludes the
possibility to resolve the converter from CDI, etc. Instead use
one of:
* Adds an AttributeConverter by an AttributeConverterDefinition
| |
| applyAttributeConverter | back to summary |
|---|---|
| public MetadataBuilder applyAttributeConverter(Class<? extends AttributeConverter<X, Y>> attributeConverterClass) Adds an AttributeConverter by its Class.
| |
| applyAttributeConverter | back to summary |
|---|---|
| public MetadataBuilder applyAttributeConverter(Class<? extends AttributeConverter<X, Y>> attributeConverterClass, boolean autoApply) Adds an AttributeConverter by its Class plus a boolean indicating whether to auto apply it.
| |
| applyAttributeConverter | back to summary |
|---|---|
| public MetadataBuilder applyAttributeConverter(AttributeConverter<X, Y> attributeConverter) Adds an AttributeConverter instance.
| |
| applyAttributeConverter | back to summary |
|---|---|
| public MetadataBuilder applyAttributeConverter(AttributeConverter<X, Y> attributeConverter, boolean autoApply) Adds an AttributeConverter instance, explicitly indicating whether to auto-apply.
| |
| applyAuxiliaryDatabaseObject | back to summary |
|---|---|
| public MetadataBuilder applyAuxiliaryDatabaseObject(AuxiliaryDatabaseObject auxiliaryDatabaseObject) | |
| applyBasicType | back to summary |
|---|---|
| public MetadataBuilder applyBasicType(BasicType type) Specify an additional or overridden basic type mapping.
| |
| applyBasicType | back to summary |
|---|---|
| public MetadataBuilder applyBasicType(BasicType type, String... keys) Specify an additional or overridden basic type mapping supplying specific registration keys.
| |
| applyBasicType | back to summary |
|---|---|
| public MetadataBuilder applyBasicType(UserType type, String... keys) Register an additional or overridden custom type mapping.
| |
| applyBasicType | back to summary |
|---|---|
| public MetadataBuilder applyBasicType(CompositeUserType type, String... keys) Register an additional or overridden composite custom type mapping.
| |
| applyCacheRegionDefinition | back to summary |
|---|---|
| public MetadataBuilder applyCacheRegionDefinition(CacheRegionDefinition cacheRegionDefinition) Apply a CacheRegionDefinition to be applied to an entity, collection or query while building the Metadata object.
| |
| applyIdGenerationTypeInterpreter | back to summary |
|---|---|
| public MetadataBuilder applyIdGenerationTypeInterpreter(IdGeneratorStrategyInterpreter interpreter) | |
| applyImplicitCatalogName | back to summary |
|---|---|
| public MetadataBuilder applyImplicitCatalogName(String implicitCatalogName) Specify the implicit catalog name to apply to any unqualified database names.
Its default is defined by the
| |
| applyImplicitNamingStrategy | back to summary |
|---|---|
| public MetadataBuilder applyImplicitNamingStrategy(ImplicitNamingStrategy namingStrategy) Specify the ImplicitNamingStrategy to use in building the Metadata.
Its default is defined by the
| |
| applyImplicitSchemaName | back to summary |
|---|---|
| public MetadataBuilder applyImplicitSchemaName(String implicitSchemaName) Specify the implicit schema name to apply to any unqualified database names.
Its default is defined by the
| |
| applyIndexView | back to summary |
|---|---|
| public MetadataBuilder applyIndexView(IndexView jandexView) Allows specifying a specific Jandex index to use for reading annotation information. It is important to understand that if a Jandex index is passed in, it is expected that this Jandex index already contains all entries for all classes. No additional indexing will be done in this case. NOTE : Here for future expansion. At the moment the passed Jandex index is not used.
| |
| applyPhysicalNamingStrategy | back to summary |
|---|---|
| public MetadataBuilder applyPhysicalNamingStrategy(PhysicalNamingStrategy namingStrategy) Specify the PhysicalNamingStrategy to use in building the Metadata.
Its default is defined by the
| |
| applyScanEnvironment | back to summary |
|---|---|
| public MetadataBuilder applyScanEnvironment(ScanEnvironment scanEnvironment) Consider this temporary as discussed on
| |
| applyScanner | back to summary |
|---|---|
| public MetadataBuilder applyScanner(Scanner scanner) Specify a particular Scanner instance to use.
Its default is defined by the
| |
| applyScanOptions | back to summary |
|---|---|
| public MetadataBuilder applyScanOptions(ScanOptions scanOptions) Specify the options to be used in performing scanning.
| |
| applySharedCacheMode | back to summary |
|---|---|
| public MetadataBuilder applySharedCacheMode(SharedCacheMode cacheMode) Specify the second-level cache mode to be used. This is the cache mode in terms of whether or not to cache.
Its default is defined by the
| |
| applySourceProcessOrdering | back to summary |
|---|---|
| public MetadataBuilder applySourceProcessOrdering(MetadataSourceType... sourceTypes) Apply a specific ordering to the processing of sources. Note that unlike most of the methods on this contract that deal with multiple values internally, this one *replaces* any already set (its more a setter) instead of adding to.
Its default is defined by the
| |
| applySqlFunction | back to summary |
|---|---|
| public MetadataBuilder applySqlFunction(String functionName, SQLFunction function) | |
| applyTempClassLoader | back to summary |
|---|---|
| public MetadataBuilder applyTempClassLoader(ClassLoader tempClassLoader) Apply a ClassLoader for use while building the Metadata.
Ideally we should avoid accessing ClassLoaders when perform 1st phase of bootstrap. This
is a ClassLoader that can be used in cases when we have to. IN EE managed environments, this
is the ClassLoader mandated by
| |
| applyTypes | back to summary |
|---|---|
| public MetadataBuilder applyTypes(TypeContributor typeContributor) Apply an explicit TypeContributor (implicit application via ServiceLoader will still happen too)
| |
| build | back to summary |
|---|---|
| public Metadata build() Actually build the metamodel
| |
| enableExplicitDiscriminatorsForJoinedSubclassSupport | back to summary |
|---|---|
| public MetadataBuilder enableExplicitDiscriminatorsForJoinedSubclassSupport(boolean enabled) Should we process or ignore explicitly defined discriminators in the case of joined-subclasses. The legacy behavior of Hibernate was to ignore the discriminator annotations because Hibernate (unlike some providers) does not need discriminators to determine the concrete type when it comes to joined inheritance. However, for portability reasons we do now allow using explicit discriminators along with joined inheritance. It is configurable though to support legacy apps.
Its default is defined by the
| |
| enableGlobalNationalizedCharacterDataSupport | back to summary |
|---|---|
| public MetadataBuilder enableGlobalNationalizedCharacterDataSupport(boolean enabled) Should nationalized variants of character data be used in the database types? For example, should
Its default is defined by the
| |
| enableImplicitDiscriminatorsForJoinedSubclassSupport | back to summary |
|---|---|
| public MetadataBuilder enableImplicitDiscriminatorsForJoinedSubclassSupport(boolean enabled) Similarly to Again the premise here is JPA portability, bearing in mind that some JPA provider need these discriminators.
Its default is defined by the
| |
| enableImplicitForcingOfDiscriminatorsInSelect | back to summary |
|---|---|
| public MetadataBuilder enableImplicitForcingOfDiscriminatorsInSelect(boolean supported) For entities which do not explicitly say, should we force discriminators into
SQL selects? The (historical) default is
Its default is defined by the
| |
| enableNewIdentifierGeneratorSupport | back to summary |
|---|---|
| public MetadataBuilder enableNewIdentifierGeneratorSupport(boolean enable) Should we enable support for the "new" (since 3.2) identifier generator mappings for handling:
Its default is defined by the
| |
| unwrap | back to summary |
|---|---|
| public <T extends MetadataBuilder> T unwrap(Class<T> type) Allows unwrapping this builder as another, more specific type.
| |