程序包 org.hibernate.loader.plan.build.internal

类 AbstractEntityGraphVisitationStrategy

java.lang.Object

org.hibernate.loader.plan.build.internal.AbstractLoadPlanBuildingAssociationVisitationStrategy

org.hibernate.loader.plan.build.internal.AbstractEntityGraphVisitationStrategy

所有已实现的接口:

LoadPlanBuildingAssociationVisitationStrategy, LoadPlanBuildingContext, AssociationVisitationStrategy

直接已知子类:

FetchGraphLoadPlanBuildingStrategy, LoadGraphLoadPlanBuildingStrategy

public abstract class AbstractEntityGraphVisitationStrategy
extends AbstractLoadPlanBuildingAssociationVisitationStrategy

Abstract strategy of building loadplan based on entity graph. The problem we're resolving here is, we have TWO trees to walk (only entity loading here):

entity metadata and its associations
entity graph and attribute nodes

And most time, the entity graph tree is partial of entity metadata tree. So, the idea here is, we walk the entity metadata tree, just as how we build the static loadplan from mappings, and we try to match the node to entity graph ( and subgraph ), if there is a match, then the attribute is fetched, it is not, then depends on which property is used to apply this entity graph.

作者:

Strong Liu , Brett Meyer

嵌套类概要

从类继承的嵌套类/接口 org.hibernate.loader.plan.build.internal.AbstractLoadPlanBuildingAssociationVisitationStrategy

AbstractLoadPlanBuildingAssociationVisitationStrategy.PropertyPathStack

字段概要

字段

修饰符和类型	字段	说明
protected static FetchStrategy	DEFAULT_EAGER	The JPA 2.1 SPEC's Entity Graph only defines _WHEN_ to load an attribute, it doesn't define _HOW_ to load it So I'm here just making an assumption that when it is EAGER, then we use JOIN, and when it is LAZY, then we use SELECT.
protected static FetchStrategy	DEFAULT_LAZY
protected LoadQueryInfluencers	loadQueryInfluencers

从类继承的字段 org.hibernate.loader.plan.build.internal.AbstractLoadPlanBuildingAssociationVisitationStrategy

currentPropertyPath

构造器概要

构造器

限定符	构造器	说明
protected	AbstractEntityGraphVisitationStrategy(SessionFactoryImplementor sessionFactory, LoadQueryInfluencers loadQueryInfluencers, LockMode lockMode)

方法概要

修饰符和类型	方法	说明
protected void	addRootReturn(Return rootReturn)
protected FetchStrategy	adjustJoinFetchIfNeeded(AssociationAttributeDefinition attributeDefinition, FetchStrategy fetchStrategy)
LoadPlan	buildLoadPlan()	After visitation is done, build the load plan.
protected FetchStrategy	determineFetchStrategy(AssociationAttributeDefinition attributeDefinition)
void	finish()	Notification we are finished visitation.
void	finishingAttribute(AttributeDefinition attributeDefinition)	Notification that we are finishing walking an attribute.
void	finishingCollectionElements(CollectionElementDefinition elementDefinition)	Notification that we are finishing walking the elements of a collection (List/Map).
void	finishingCollectionIndex(CollectionIndexDefinition indexDefinition)	Notification that we are finishing walking the index of a collection (List/Map).
void	foundCircularAssociation(AssociationAttributeDefinition attributeDefinition)
protected abstract GraphImplementor	getRootEntityGraph()
protected abstract FetchStrategy	resolveImplicitFetchStrategyFromEntityGraph(AssociationAttributeDefinition attributeDefinition)
void	start()	Notification we are preparing to start visitation.
boolean	startingAttribute(AttributeDefinition attributeDefinition)	I'm using the NULL-OBJECT pattern here.
void	startingCollectionElements(CollectionElementDefinition elementDefinition)	Notification that we are starting to look at the element definition for the collection.
void	startingCollectionIndex(CollectionIndexDefinition indexDefinition)	Notification that we are starting to walk the index of a collection (List/Map).
protected boolean	supportsRootCollectionReturns()

从类继承的方法 org.hibernate.loader.plan.build.internal.AbstractLoadPlanBuildingAssociationVisitationStrategy

associationKeyRegistered, currentDepth, currentSource, finishingCollection, finishingComposite, finishingEntity, finishingEntityIdentifier, foundAny, getQuerySpaces, getSessionFactory, handleAssociationAttribute, handleCompositeAttribute, isDuplicateAssociationKey, isTooManyCollections, registeredFetchSource, sessionFactory, startingCollection, startingComposite, startingEntity, startingEntityIdentifier, supportsRootEntityReturns

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

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

字段详细资料

DEFAULT_EAGER

protected static final FetchStrategy DEFAULT_EAGER

The JPA 2.1 SPEC's Entity Graph only defines _WHEN_ to load an attribute, it doesn't define _HOW_ to load it So I'm here just making an assumption that when it is EAGER, then we use JOIN, and when it is LAZY, then we use SELECT. NOTE: this may be changed in the near further, though ATM I have no idea how this will be changed to :) -- stliu

DEFAULT_LAZY

protected static final FetchStrategy DEFAULT_LAZY

loadQueryInfluencers

protected final LoadQueryInfluencers loadQueryInfluencers

构造器详细资料

AbstractEntityGraphVisitationStrategy

protected AbstractEntityGraphVisitationStrategy(SessionFactoryImplementor sessionFactory,
                                                LoadQueryInfluencers loadQueryInfluencers,
                                                LockMode lockMode)

方法详细资料

start

public void start()

从接口复制的说明: AssociationVisitationStrategy

Notification we are preparing to start visitation.

指定者:

start 在接口中 AssociationVisitationStrategy

覆盖:

start 在类中 AbstractLoadPlanBuildingAssociationVisitationStrategy

finish

public void finish()

从接口复制的说明: AssociationVisitationStrategy

Notification we are finished visitation.

指定者:

finish 在接口中 AssociationVisitationStrategy

覆盖:

finish 在类中 AbstractLoadPlanBuildingAssociationVisitationStrategy

startingAttribute

public boolean startingAttribute(AttributeDefinition attributeDefinition)

I'm using the NULL-OBJECT pattern here. For attributes that don't exist in the EntityGraph, a predefined NULL-ATTRIBUTE-NODE is pushed to the stack. And for a nonexistent subgraph, a predefined NULL-SUBGRAPH is pushed to the stack. So, whenever we start visiting an attribute, there will be an attribute node pushed to the attribute stack, and a subgraph node pushed to the graph stack. when we finish visiting an attribute, these two will be popped from each stack.

指定者:

startingAttribute 在接口中 AssociationVisitationStrategy

覆盖:

startingAttribute 在类中 AbstractLoadPlanBuildingAssociationVisitationStrategy

参数:

attributeDefinition - The attribute we are preparing to walk.

返回:

true if the walking should continue; false if walking should stop.

finishingAttribute

public void finishingAttribute(AttributeDefinition attributeDefinition)

从接口复制的说明: AssociationVisitationStrategy

Notification that we are finishing walking an attribute.

指定者:

finishingAttribute 在接口中 AssociationVisitationStrategy

覆盖:

finishingAttribute 在类中 AbstractLoadPlanBuildingAssociationVisitationStrategy

参数:

attributeDefinition - The attribute we are done walking

startingCollectionElements

public void startingCollectionElements(CollectionElementDefinition elementDefinition)

从接口复制的说明: AssociationVisitationStrategy

Notification that we are starting to look at the element definition for the collection. If the collection elements are entities this will be followed up by a call to AssociationVisitationStrategy.startingEntity(org.hibernate.persister.walking.spi.EntityDefinition)

指定者:

startingCollectionElements 在接口中 AssociationVisitationStrategy

覆盖:

startingCollectionElements 在类中 AbstractLoadPlanBuildingAssociationVisitationStrategy

参数:

elementDefinition - The collection element we are preparing to walk..

finishingCollectionElements

public void finishingCollectionElements(CollectionElementDefinition elementDefinition)

从接口复制的说明: AssociationVisitationStrategy

Notification that we are finishing walking the elements of a collection (List/Map).

指定者:

finishingCollectionElements 在接口中 AssociationVisitationStrategy

覆盖:

finishingCollectionElements 在类中 AbstractLoadPlanBuildingAssociationVisitationStrategy

参数:

elementDefinition - The collection element we are finishing

startingCollectionIndex

public void startingCollectionIndex(CollectionIndexDefinition indexDefinition)

从接口复制的说明: AssociationVisitationStrategy

Notification that we are starting to walk the index of a collection (List/Map). In the case of a Map, if the indices (the keys) are entities this will be followed up by a call to AssociationVisitationStrategy.startingEntity(org.hibernate.persister.walking.spi.EntityDefinition)

指定者:

startingCollectionIndex 在接口中 AssociationVisitationStrategy

覆盖:

startingCollectionIndex 在类中 AbstractLoadPlanBuildingAssociationVisitationStrategy

参数:

indexDefinition - The collection index we are preparing to walk.

finishingCollectionIndex

public void finishingCollectionIndex(CollectionIndexDefinition indexDefinition)

从接口复制的说明: AssociationVisitationStrategy

Notification that we are finishing walking the index of a collection (List/Map).

指定者:

finishingCollectionIndex 在接口中 AssociationVisitationStrategy

覆盖:

finishingCollectionIndex 在类中 AbstractLoadPlanBuildingAssociationVisitationStrategy

参数:

indexDefinition - The collection index we are finishing

supportsRootCollectionReturns

protected boolean supportsRootCollectionReturns()

覆盖:

supportsRootCollectionReturns 在类中 AbstractLoadPlanBuildingAssociationVisitationStrategy

addRootReturn

protected void addRootReturn(Return rootReturn)

指定者:

addRootReturn 在类中 AbstractLoadPlanBuildingAssociationVisitationStrategy

determineFetchStrategy

protected FetchStrategy determineFetchStrategy(AssociationAttributeDefinition attributeDefinition)

指定者:

determineFetchStrategy 在类中 AbstractLoadPlanBuildingAssociationVisitationStrategy

resolveImplicitFetchStrategyFromEntityGraph

protected abstract FetchStrategy resolveImplicitFetchStrategyFromEntityGraph(AssociationAttributeDefinition attributeDefinition)

adjustJoinFetchIfNeeded

protected FetchStrategy adjustJoinFetchIfNeeded(AssociationAttributeDefinition attributeDefinition,
                                                FetchStrategy fetchStrategy)

buildLoadPlan

public LoadPlan buildLoadPlan()

从接口复制的说明: LoadPlanBuildingAssociationVisitationStrategy

After visitation is done, build the load plan.

返回:

The load plan

getRootEntityGraph

protected abstract GraphImplementor getRootEntityGraph()

foundCircularAssociation

public void foundCircularAssociation(AssociationAttributeDefinition attributeDefinition)

指定者:

foundCircularAssociation 在接口中 AssociationVisitationStrategy

覆盖:

foundCircularAssociation 在类中 AbstractLoadPlanBuildingAssociationVisitationStrategy