Class ShadowReferenceAttributeDefinitionImpl

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, PrismItemMiscDefinition, PrismItemStorageDefinition, PrismItemStorageDefinition.Mutable, PrismLifecycleDefinition, PrismLifecycleDefinition.Mutable, PrismPresentationDefinition, PrismPresentationDefinition.Mutable, Revivable, SmartVisitable<Definition>, Visitable<Definition>, LayeredDefinition, ResourceObjectInboundDefinition.ItemInboundDefinition, ShadowAttributeDefinition<ShadowReferenceAttribute,ShadowAssociationValueType>, ShadowItemLayeredDefinition, ShadowItemLifecycleDefinitionDefaults, ShadowItemUcfDefinition, ShadowReferenceAttributeDefinition, DebugDumpable, ShortDumpable, Serializable, Cloneable

Definition of a shadow association item, e.g., `ri:group`. Note that unlike the attributes, here the ShadowAttributeDefinitionImpl.nativeDefinition may be generated artificially based on simulated ReferencesCapabilityType definition. TODO various options for configuring associations TODO Effectively immutable? (if constituent definitions are immutable), except for the ability of changing the maxOccurs value. - is this still true?
See Also: