Class ShadowAssociationDefinitionImpl

java.lang.Object
com.evolveum.midpoint.prism.AbstractFreezable
com.evolveum.midpoint.schema.processor.ShadowAssociationDefinitionImpl
All Implemented Interfaces:
Definition, Definition.DefinitionMutator, Freezable, ItemDefinition<PrismContainer<ShadowAssociationValueType>>, ItemDefinition.ItemDefinitionMutator, LivePrismItemDefinition, LocalItemDefinitionStore, PrismContainerDefinition<ShadowAssociationValueType>, PrismContainerDefinition.PrismContainerDefinitionMutator<ShadowAssociationValueType>, PrismItemAccessDefinition, PrismItemAccessDefinition.Mutable, PrismItemBasicDefinition, PrismItemBasicDefinition.Mutable, PrismItemStorageDefinition, PrismItemStorageDefinition.Mutable, PrismLifecycleDefinition, PrismLifecycleDefinition.Mutable, PrismPresentationDefinition, PrismPresentationDefinition.Mutable, Revivable, SchemaLookup.Aware, SmartVisitable<Definition>, Visitable<Definition>, ResourceObjectInboundProcessingDefinition.ItemInboundProcessingDefinition, ShadowAssociationDefinition, ShadowItemDefinition, ShadowItemLayeredDefinition, DebugDumpable, Serializable, Cloneable

The (currently) only implementation of ShadowAssociationDefinition. This object is effectively immutable, but only after the whole resource schema is frozen. The reason is that the referenced attribute and object definitions are mutable during schema parsing. The exception is maxOccurs that can be changed even after the schema is frozen. (But not after this particular object is frozen.) It is because the GUI needs it that way.
See Also: