java.lang.Object
- org.hibernate.boot.spi.AbstractDelegatingMetadataBuilderImplementor<T>

类型参数:

T - The type of a specific sub-class; Allows sub-classes to narrow down the return-type of the contract methods to a specialization of MetadataBuilderImplementor

所有已实现的接口:

MetadataBuilder, MetadataBuilderImplementor
```
public abstract class AbstractDelegatingMetadataBuilderImplementor<T extends MetadataBuilderImplementor>
extends Object
implements MetadataBuilderImplementor
```
Convenience base class for custom implementors of MetadataBuilderImplementor using delegation.

作者:

Gunnar Morling

构造器概要

构造器
构造器说明

AbstractDelegatingMetadataBuilderImplementor(MetadataBuilderImplementor delegate)

方法概要

所有方法实例方法抽象方法具体方法已过时的方法
修饰符和类型	方法	说明
`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.
`MetadataBuilder`	`applyArchiveDescriptorFactory(ArchiveDescriptorFactory factory)`	Specify a particular ArchiveDescriptorFactory instance to use in scanning.
`MetadataBuilder`	`applyAttributeConverter(Class<? extends javax.persistence.AttributeConverter> attributeConverterClass)`	Adds an AttributeConverter by its Class.
`MetadataBuilder`	`applyAttributeConverter(Class<? extends javax.persistence.AttributeConverter> attributeConverterClass, boolean autoApply)`	Adds an AttributeConverter by its Class plus a boolean indicating whether to auto apply it.
`MetadataBuilder`	`applyAttributeConverter(javax.persistence.AttributeConverter attributeConverter)`	Adds an AttributeConverter instance.
`MetadataBuilder`	`applyAttributeConverter(javax.persistence.AttributeConverter attributeConverter, boolean autoApply)`	Adds an AttributeConverter instance, explicitly indicating whether to auto-apply.
`MetadataBuilder`	`applyAttributeConverter(AttributeConverterDefinition definition)`	Adds an AttributeConverter by an AttributeConverterDefinition
`MetadataBuilder`	`applyAuxiliaryDatabaseObject(AuxiliaryDatabaseObject auxiliaryDatabaseObject)`
`MetadataBuilder`	`applyBasicType(BasicType type)`	Specify an additional or overridden basic type mapping.
`MetadataBuilder`	`applyBasicType(BasicType type, String... keys)`	Specify an additional or overridden basic type mapping supplying specific registration keys.
`MetadataBuilder`	`applyBasicType(CompositeUserType type, String... keys)`	Register an additional or overridden composite custom type mapping.
`MetadataBuilder`	`applyBasicType(UserType type, String... keys)`	Register an additional or overridden custom type mapping.
`MetadataBuilder`	`applyCacheRegionDefinition(CacheRegionDefinition cacheRegionDefinition)`	Apply a CacheRegionDefinition to be applied to an entity, collection or query while building the Metadata object.
`MetadataBuilder`	`applyIdGenerationTypeInterpreter(IdGeneratorStrategyInterpreter interpreter)`
`MetadataBuilder`	`applyImplicitCatalogName(String implicitCatalogName)`	Specify the implicit catalog name to apply to any unqualified database names.
`MetadataBuilder`	`applyImplicitNamingStrategy(ImplicitNamingStrategy namingStrategy)`	Specify the ImplicitNamingStrategy to use in building the Metadata.
`MetadataBuilder`	`applyImplicitSchemaName(String implicitSchemaName)`	Specify the implicit schema name to apply to any unqualified database names.
`MetadataBuilder`	`applyIndexView(org.jboss.jandex.IndexView jandexView)`	Allows specifying a specific Jandex index to use for reading annotation information.
`MetadataBuilder`	`applyPhysicalNamingStrategy(PhysicalNamingStrategy namingStrategy)`	Specify the PhysicalNamingStrategy to use in building the Metadata.
`MetadataBuilder`	`applyScanEnvironment(ScanEnvironment scanEnvironment)`	Consider this temporary as discussed on `ScanEnvironment`
`MetadataBuilder`	`applyScanner(Scanner scanner)`	Specify a particular Scanner instance to use.
`MetadataBuilder`	`applyScanOptions(ScanOptions scanOptions)`	Specify the options to be used in performing scanning.
`MetadataBuilder`	`applySharedCacheMode(javax.persistence.SharedCacheMode cacheMode)`	Specify the second-level cache mode to be used.
`MetadataBuilder`	`applySourceProcessOrdering(MetadataSourceType... sourceTypes)`	Apply a specific ordering to the processing of sources.
`MetadataBuilder`	`applySqlFunction(String functionName, SQLFunction function)`
`MetadataBuilder`	`applyTempClassLoader(ClassLoader tempClassLoader)`	Apply a ClassLoader for use while building the Metadata.
`MetadataBuilder`	`applyTypes(TypeContributor typeContributor)`	Apply an explicit TypeContributor (implicit application via ServiceLoader will still happen too)
`Metadata`	`build()`	Actually build the metamodel
`protected MetadataBuilderImplementor`	`delegate()`
`MetadataBuilder`	`enableExplicitDiscriminatorsForJoinedSubclassSupport(boolean enabled)`	Should we process or ignore explicitly defined discriminators in the case of joined-subclasses.
`MetadataBuilder`	`enableGlobalNationalizedCharacterDataSupport(boolean enabled)`	Should nationalized variants of character data be used in the database types?
`MetadataBuilder`	`enableImplicitDiscriminatorsForJoinedSubclassSupport(boolean enabled)`	Similarly to `MetadataBuilder.enableExplicitDiscriminatorsForJoinedSubclassSupport(boolean)`, but here how should we treat joined inheritance when there is no explicitly defined discriminator annotations?
`MetadataBuilder`	`enableImplicitForcingOfDiscriminatorsInSelect(boolean supported)`	For entities which do not explicitly say, should we force discriminators into SQL selects?
`MetadataBuilder`	`enableNewIdentifierGeneratorSupport(boolean enable)`	Should we enable support for the "new" (since 3.2) identifier generator mappings for handling: `GenerationType.SEQUENCE` `GenerationType.IDENTITY` `GenerationType.TABLE` `GenerationType.AUTO`
`MetadataBuilderImplementor`	`getDelegate()`	已过时。 use `delegate()` instead
`MetadataBuildingOptions`	`getMetadataBuildingOptions()`	Get the options being collected on this MetadataBuilder that will ultimately be used in building the Metadata.
`protected abstract T`	`getThis()`	Returns a specific implementation.
`<M extends MetadataBuilder> M`	`unwrap(Class<M> type)`	Allows unwrapping this builder as another, more specific type.

从类继承的方法 java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

从接口继承的方法 org.hibernate.boot.spi.MetadataBuilderImplementor
getBootstrapContext

- 构造器详细资料
  - AbstractDelegatingMetadataBuilderImplementor
```
public AbstractDelegatingMetadataBuilderImplementor(MetadataBuilderImplementor delegate)
```
- 方法详细资料
  - getDelegate
```
@Deprecated
public MetadataBuilderImplementor getDelegate()
```
    已过时。
    use delegate() instead
    
    Kept for compatibility reason but should be removed as soon as possible.
  - delegate
```
protected MetadataBuilderImplementor delegate()
```
  - getThis
```
protected abstract T getThis()
```
    Returns a specific implementation. See the What is the "getThis trick?".
  - applyImplicitSchemaName
```
public MetadataBuilder applyImplicitSchemaName(String implicitSchemaName)
```
    从接口复制的说明: MetadataBuilder
    
    Specify the implicit schema name to apply to any unqualified database names.
    Its default is defined by the AvailableSettings.DEFAULT_SCHEMA setting if using property-based configuration.
    
    指定者:
    
    applyImplicitSchemaName 在接口中 MetadataBuilder
    
    参数:
    
    implicitSchemaName - The implicit schema name
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.DEFAULT_SCHEMA
  - applyImplicitCatalogName
```
public MetadataBuilder applyImplicitCatalogName(String implicitCatalogName)
```
    从接口复制的说明: MetadataBuilder
    
    Specify the implicit catalog name to apply to any unqualified database names.
    Its default is defined by the AvailableSettings.DEFAULT_CATALOG setting if using property-based configuration.
    
    指定者:
    
    applyImplicitCatalogName 在接口中 MetadataBuilder
    
    参数:
    
    implicitCatalogName - The implicit catalog name
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.DEFAULT_CATALOG
  - applyImplicitNamingStrategy
```
public MetadataBuilder applyImplicitNamingStrategy(ImplicitNamingStrategy namingStrategy)
```
    从接口复制的说明: MetadataBuilder
    
    Specify the ImplicitNamingStrategy to use in building the Metadata.
    Its default is defined by the AvailableSettings.IMPLICIT_NAMING_STRATEGY setting if using property-based configuration.
    
    指定者:
    
    applyImplicitNamingStrategy 在接口中 MetadataBuilder
    
    参数:
    
    namingStrategy - The ImplicitNamingStrategy to apply
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.IMPLICIT_NAMING_STRATEGY
  - applyPhysicalNamingStrategy
```
public MetadataBuilder applyPhysicalNamingStrategy(PhysicalNamingStrategy namingStrategy)
```
    从接口复制的说明: MetadataBuilder
    
    Specify the PhysicalNamingStrategy to use in building the Metadata.
    Its default is defined by the AvailableSettings.PHYSICAL_NAMING_STRATEGY setting if using property-based configuration.
    
    指定者:
    
    applyPhysicalNamingStrategy 在接口中 MetadataBuilder
    
    参数:
    
    namingStrategy - The PhysicalNamingStrategy to apply
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.PHYSICAL_NAMING_STRATEGY
  - applySharedCacheMode
```
public MetadataBuilder applySharedCacheMode(javax.persistence.SharedCacheMode cacheMode)
```
    从接口复制的说明: MetadataBuilder
    
    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 javax.persistence.sharedCache.mode setting if using property-based configuration.
    
    指定者:
    
    applySharedCacheMode 在接口中 MetadataBuilder
    
    参数:
    
    cacheMode - The cache mode.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    MetadataBuilder.applyAccessType(org.hibernate.cache.spi.access.AccessType)
  - applyAccessType
```
public MetadataBuilder applyAccessType(AccessType accessType)
```
    从接口复制的说明: MetadataBuilder
    
    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 AvailableSettings.DEFAULT_CACHE_CONCURRENCY_STRATEGY setting if using property-based configuration.
    
    指定者:
    
    applyAccessType 在接口中 MetadataBuilder
    
    参数:
    
    accessType - The access-type to use as default.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.DEFAULT_CACHE_CONCURRENCY_STRATEGY, MetadataBuilder.applySharedCacheMode(javax.persistence.SharedCacheMode)
  - applyIndexView
```
public MetadataBuilder applyIndexView(org.jboss.jandex.IndexView jandexView)
```
    从接口复制的说明: MetadataBuilder
    
    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.
    
    指定者:
    
    applyIndexView 在接口中 MetadataBuilder
    
    参数:
    
    jandexView - The Jandex index to use.
    
    返回:
    
    this, for method chaining
  - applyScanOptions
```
public MetadataBuilder applyScanOptions(ScanOptions scanOptions)
```
    从接口复制的说明: MetadataBuilder
    
    Specify the options to be used in performing scanning.
    
    指定者:
    
    applyScanOptions 在接口中 MetadataBuilder
    
    参数:
    
    scanOptions - The scan options.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.SCANNER_DISCOVERY
  - applyScanEnvironment
```
public MetadataBuilder applyScanEnvironment(ScanEnvironment scanEnvironment)
```
    从接口复制的说明: MetadataBuilder
    
    Consider this temporary as discussed on ScanEnvironment
    
    指定者:
    
    applyScanEnvironment 在接口中 MetadataBuilder
    
    参数:
    
    scanEnvironment - The environment for scanning
    
    返回:
    
    this, for method chaining
  - applyScanner
```
public MetadataBuilder applyScanner(Scanner scanner)
```
    从接口复制的说明: MetadataBuilder
    
    Specify a particular Scanner instance to use.
    Its default is defined by the AvailableSettings.SCANNER setting if using property-based configuration.
    
    指定者:
    
    applyScanner 在接口中 MetadataBuilder
    
    参数:
    
    scanner - The scanner to use.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.SCANNER
  - applyArchiveDescriptorFactory
```
public MetadataBuilder applyArchiveDescriptorFactory(ArchiveDescriptorFactory factory)
```
    从接口复制的说明: MetadataBuilder
    
    Specify a particular ArchiveDescriptorFactory instance to use in scanning.
    Its default is defined by the AvailableSettings.SCANNER_ARCHIVE_INTERPRETER setting if using property-based configuration.
    
    指定者:
    
    applyArchiveDescriptorFactory 在接口中 MetadataBuilder
    
    参数:
    
    factory - The ArchiveDescriptorFactory to use.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.SCANNER_ARCHIVE_INTERPRETER
  - enableNewIdentifierGeneratorSupport
```
public MetadataBuilder enableNewIdentifierGeneratorSupport(boolean enable)
```
    从接口复制的说明: MetadataBuilder
    Should we enable support for the "new" (since 3.2) identifier generator mappings for handling:
    
    GenerationType.SEQUENCE
    
    GenerationType.IDENTITY
    
    GenerationType.TABLE
    
    GenerationType.AUTO
    
    Its default is defined by the AvailableSettings.USE_NEW_ID_GENERATOR_MAPPINGS setting if using property-based configuration.
    指定者:
    
    enableNewIdentifierGeneratorSupport 在接口中 MetadataBuilder
    
    参数:
    
    enable - true to enable; false to disable; don't call for default.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.USE_NEW_ID_GENERATOR_MAPPINGS
  - enableExplicitDiscriminatorsForJoinedSubclassSupport
```
public MetadataBuilder enableExplicitDiscriminatorsForJoinedSubclassSupport(boolean enabled)
```
    从接口复制的说明: MetadataBuilder
    
    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 AvailableSettings.IGNORE_EXPLICIT_DISCRIMINATOR_COLUMNS_FOR_JOINED_SUBCLASS setting if using property-based configuration.
    
    指定者:
    
    enableExplicitDiscriminatorsForJoinedSubclassSupport 在接口中 MetadataBuilder
    
    参数:
    
    enabled - Should processing (not ignoring) explicit discriminators be enabled?
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.IGNORE_EXPLICIT_DISCRIMINATOR_COLUMNS_FOR_JOINED_SUBCLASS
  - enableImplicitDiscriminatorsForJoinedSubclassSupport
```
public MetadataBuilder enableImplicitDiscriminatorsForJoinedSubclassSupport(boolean enabled)
```
    从接口复制的说明: MetadataBuilder
    
    Similarly to MetadataBuilder.enableExplicitDiscriminatorsForJoinedSubclassSupport(boolean), but here how should we treat joined inheritance when there is no explicitly defined discriminator annotations? If enabled, we will handle joined inheritance with no explicit discriminator annotations by implicitly creating one (following the JPA implicit naming rules).
    Again the premise here is JPA portability, bearing in mind that some JPA provider need these discriminators.
    Its default is defined by the AvailableSettings.IMPLICIT_DISCRIMINATOR_COLUMNS_FOR_JOINED_SUBCLASS setting if using property-based configuration.
    
    指定者:
    
    enableImplicitDiscriminatorsForJoinedSubclassSupport 在接口中 MetadataBuilder
    
    参数:
    
    enabled - Should we implicitly create discriminator for joined inheritance if one is not explicitly mentioned?
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.IMPLICIT_DISCRIMINATOR_COLUMNS_FOR_JOINED_SUBCLASS
  - enableImplicitForcingOfDiscriminatorsInSelect
```
public MetadataBuilder enableImplicitForcingOfDiscriminatorsInSelect(boolean supported)
```
    从接口复制的说明: MetadataBuilder
    
    For entities which do not explicitly say, should we force discriminators into SQL selects? The (historical) default is false
    Its default is defined by the AvailableSettings.FORCE_DISCRIMINATOR_IN_SELECTS_BY_DEFAULT setting if using property-based configuration.
    
    指定者:
    
    enableImplicitForcingOfDiscriminatorsInSelect 在接口中 MetadataBuilder
    
    参数:
    
    supported - true indicates we will force the discriminator into the select; false indicates we will not.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.FORCE_DISCRIMINATOR_IN_SELECTS_BY_DEFAULT
  - enableGlobalNationalizedCharacterDataSupport
```
public MetadataBuilder enableGlobalNationalizedCharacterDataSupport(boolean enabled)
```
    从接口复制的说明: MetadataBuilder
    
    Should nationalized variants of character data be used in the database types? For example, should NVARCHAR be used instead of VARCHAR? NCLOB instead of CLOB?
    Its default is defined by the AvailableSettings.USE_NATIONALIZED_CHARACTER_DATA setting if using property-based configuration.
    
    指定者:
    
    enableGlobalNationalizedCharacterDataSupport 在接口中 MetadataBuilder
    
    参数:
    
    enabled - true says to use nationalized variants; false says to use the non-nationalized variants.
    
    返回:
    
    this, for method chaining
    
    另请参阅:
    
    AvailableSettings.USE_NATIONALIZED_CHARACTER_DATA
  - applyBasicType
```
public MetadataBuilder applyBasicType(BasicType type)
```
    从接口复制的说明: MetadataBuilder
    
    Specify an additional or overridden basic type mapping.
    
    指定者:
    
    applyBasicType 在接口中 MetadataBuilder
    
    参数:
    
    type - The type addition or override.
    
    返回:
    
    this, for method chaining
  - applyBasicType
```
public MetadataBuilder applyBasicType(BasicType type,
                                      String... keys)
```
    从接口复制的说明: MetadataBuilder
    
    Specify an additional or overridden basic type mapping supplying specific registration keys.
    
    指定者:
    
    applyBasicType 在接口中 MetadataBuilder
    
    参数:
    
    type - The type addition or override.
    
    keys - The keys under which to register the basic type.
    
    返回:
    
    this, for method chaining
  - applyBasicType
```
public MetadataBuilder applyBasicType(UserType type,
                                      String... keys)
```
    从接口复制的说明: MetadataBuilder
    
    Register an additional or overridden custom type mapping.
    
    指定者:
    
    applyBasicType 在接口中 MetadataBuilder
    
    参数:
    
    type - The custom type
    
    keys - The keys under which to register the custom type.
    
    返回:
    
    this, for method chaining
  - applyBasicType
```
public MetadataBuilder applyBasicType(CompositeUserType type,
                                      String... keys)
```
    从接口复制的说明: MetadataBuilder
    
    Register an additional or overridden composite custom type mapping.
    
    指定者:
    
    applyBasicType 在接口中 MetadataBuilder
    
    参数:
    
    type - The composite custom type
    
    keys - The keys under which to register the composite custom type.
    
    返回:
    
    this, for method chaining
  - applyTypes
```
public MetadataBuilder applyTypes(TypeContributor typeContributor)
```
    从接口复制的说明: MetadataBuilder
    
    Apply an explicit TypeContributor (implicit application via ServiceLoader will still happen too)
    
    指定者:
    
    applyTypes 在接口中 MetadataBuilder
    
    参数:
    
    typeContributor - The contributor to apply
    
    返回:
    
    this, for method chaining
  - applyCacheRegionDefinition
```
public MetadataBuilder applyCacheRegionDefinition(CacheRegionDefinition cacheRegionDefinition)
```
    从接口复制的说明: MetadataBuilder
    
    Apply a CacheRegionDefinition to be applied to an entity, collection or query while building the Metadata object.
    
    指定者:
    
    applyCacheRegionDefinition 在接口中 MetadataBuilder
    
    参数:
    
    cacheRegionDefinition - The cache region definition to apply
    
    返回:
    
    this, for method chaining
  - applyTempClassLoader
```
public MetadataBuilder applyTempClassLoader(ClassLoader tempClassLoader)
```
    从接口复制的说明: MetadataBuilder
    
    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 PersistenceUnitInfo.getNewTempClassLoader(). This ClassLoader is thrown away by the container afterwards. The idea being that the Class can still be enhanced in the application ClassLoader. In other environments, pass a ClassLoader that performs the same function if desired.
    
    指定者:
    
    applyTempClassLoader 在接口中 MetadataBuilder
    
    参数:
    
    tempClassLoader - ClassLoader for use during building the Metadata
    
    返回:
    
    this, for method chaining
  - applySourceProcessOrdering
```
public MetadataBuilder applySourceProcessOrdering(MetadataSourceType... sourceTypes)
```
    从接口复制的说明: MetadataBuilder
    
    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 AvailableSettings.ARTIFACT_PROCESSING_ORDER setting if using property-based configuration.
    
    指定者:
    
    applySourceProcessOrdering 在接口中 MetadataBuilder
    
    参数:
    
    sourceTypes - The types, in the order they should be processed
    
    返回:
    
    this for method chaining
    
    另请参阅:
    
    AvailableSettings.ARTIFACT_PROCESSING_ORDER
  - applySqlFunction
```
public MetadataBuilder applySqlFunction(String functionName,
                                        SQLFunction function)
```
    指定者:
    
    applySqlFunction 在接口中 MetadataBuilder
  - applyAuxiliaryDatabaseObject
```
public MetadataBuilder applyAuxiliaryDatabaseObject(AuxiliaryDatabaseObject auxiliaryDatabaseObject)
```
    指定者:
    
    applyAuxiliaryDatabaseObject 在接口中 MetadataBuilder
  - applyAttributeConverter
```
public MetadataBuilder applyAttributeConverter(AttributeConverterDefinition definition)
```
    从接口复制的说明: MetadataBuilder
    
    Adds an AttributeConverter by an AttributeConverterDefinition
    
    指定者:
    
    applyAttributeConverter 在接口中 MetadataBuilder
    
    参数:
    
    definition - The definition
    
    返回:
    
    this for method chaining
  - applyAttributeConverter
```
public MetadataBuilder applyAttributeConverter(Class<? extends javax.persistence.AttributeConverter> attributeConverterClass)
```
    从接口复制的说明: MetadataBuilder
    
    Adds an AttributeConverter by its Class.
    
    指定者:
    
    applyAttributeConverter 在接口中 MetadataBuilder
    
    参数:
    
    attributeConverterClass - The AttributeConverter class.
    
    返回:
    
    this for method chaining
  - applyAttributeConverter
```
public MetadataBuilder applyAttributeConverter(Class<? extends javax.persistence.AttributeConverter> attributeConverterClass,
                                               boolean autoApply)
```
    从接口复制的说明: MetadataBuilder
    
    Adds an AttributeConverter by its Class plus a boolean indicating whether to auto apply it.
    
    指定者:
    
    applyAttributeConverter 在接口中 MetadataBuilder
    
    参数:
    
    attributeConverterClass - The AttributeConverter class.
    
    autoApply - Should the AttributeConverter be auto applied to property types as specified by its "entity attribute" parameterized type?
    
    返回:
    
    this for method chaining
    
    另请参阅:
    
    AttributeConverterDefinition.from(Class, boolean)
  - applyAttributeConverter
```
public MetadataBuilder applyAttributeConverter(javax.persistence.AttributeConverter attributeConverter)
```
    从接口复制的说明: MetadataBuilder
    
    Adds an AttributeConverter instance.
    
    指定者:
    
    applyAttributeConverter 在接口中 MetadataBuilder
    
    参数:
    
    attributeConverter - The AttributeConverter instance.
    
    返回:
    
    this for method chaining
    
    另请参阅:
    
    AttributeConverterDefinition.from(AttributeConverter)
  - applyAttributeConverter
```
public MetadataBuilder applyAttributeConverter(javax.persistence.AttributeConverter attributeConverter,
                                               boolean autoApply)
```
    从接口复制的说明: MetadataBuilder
    
    Adds an AttributeConverter instance, explicitly indicating whether to auto-apply.
    
    指定者:
    
    applyAttributeConverter 在接口中 MetadataBuilder
    
    参数:
    
    attributeConverter - The AttributeConverter instance.
    
    autoApply - Should the AttributeConverter be auto applied to property types as specified by its "entity attribute" parameterized type?
    
    返回:
    
    this for method chaining
    
    另请参阅:
    
    AttributeConverterDefinition.from(AttributeConverter, boolean)
  - applyIdGenerationTypeInterpreter
```
public MetadataBuilder applyIdGenerationTypeInterpreter(IdGeneratorStrategyInterpreter interpreter)
```
    指定者:
    
    applyIdGenerationTypeInterpreter 在接口中 MetadataBuilder
  - unwrap
```
public <M extends MetadataBuilder> M unwrap(Class<M> type)
```
    从接口复制的说明: MetadataBuilder
    
    Allows unwrapping this builder as another, more specific type.
    
    指定者:
    
    unwrap 在接口中 MetadataBuilder
    
    返回:
    
    The unwrapped builder.
  - getMetadataBuildingOptions
```
public MetadataBuildingOptions getMetadataBuildingOptions()
```
    从接口复制的说明: MetadataBuilderImplementor
    
    Get the options being collected on this MetadataBuilder that will ultimately be used in building the Metadata.
    
    指定者:
    
    getMetadataBuildingOptions 在接口中 MetadataBuilderImplementor
    
    返回:
    
    The current building options
  - build
```
public Metadata build()
```
    从接口复制的说明: MetadataBuilder
    
    Actually build the metamodel
    
    指定者:
    
    build 在接口中 MetadataBuilder
    
    返回:
    
    The built metadata.

类 AbstractDelegatingMetadataBuilderImplementor<T extends MetadataBuilderImplementor>

构造器概要

方法概要

从类继承的方法 java.lang.Object

从接口继承的方法 org.hibernate.boot.spi.MetadataBuilderImplementor

构造器详细资料

AbstractDelegatingMetadataBuilderImplementor

方法详细资料

getDelegate

delegate

getThis

applyImplicitSchemaName

applyImplicitCatalogName

applyImplicitNamingStrategy

applyPhysicalNamingStrategy

applySharedCacheMode

applyAccessType

applyIndexView

applyScanOptions

applyScanEnvironment

applyScanner

applyArchiveDescriptorFactory

enableNewIdentifierGeneratorSupport

enableExplicitDiscriminatorsForJoinedSubclassSupport

enableImplicitDiscriminatorsForJoinedSubclassSupport

enableImplicitForcingOfDiscriminatorsInSelect

enableGlobalNationalizedCharacterDataSupport

applyBasicType

applyBasicType

applyBasicType

applyBasicType

applyTypes

applyCacheRegionDefinition

applyTempClassLoader

applySourceProcessOrdering

applySqlFunction

applyAuxiliaryDatabaseObject

applyAttributeConverter

applyAttributeConverter

applyAttributeConverter

applyAttributeConverter

applyAttributeConverter

applyIdGenerationTypeInterpreter

unwrap

getMetadataBuildingOptions

build