Package com.evolveum.midpoint.xml.ns._public.common.common_3

Enum ShadowLifecycleStateType

  • All Implemented Interfaces:
    Serializable, Comparable<ShadowLifecycleStateType>
    public enum ShadowLifecycleStateType
extends Enum<ShadowLifecycleStateType>

    Java class for ShadowLifecycleStateType.

    The following schema fragment specifies the expected content contained within this class. 

     <simpleType name="ShadowLifecycleStateType">
   <restriction base="{http://www.w3.org/2001/XMLSchema}string">
     <enumeration value="proposed"/>
     <enumeration value="conceived"/>
     <enumeration value="gestating"/>
     <enumeration value="live"/>
     <enumeration value="reaping"/>
     <enumeration value="corpse"/>
     <enumeration value="tombstone"/>
   </restriction>
 </simpleType>

    • Enum Constant Detail

      • PROPOSED

        public static final ShadowLifecycleStateType PROPOSED
        "Add" operation is requested. But it was not started yet. We are processing the request. This is used mostly to detect uniqueness conflicts (to "reserve" identifiers).

      • CONCEIVED

        public static final ShadowLifecycleStateType CONCEIVED
        Signal to create the resource object was sent. It is being executed.

      • GESTATING

        public static final ShadowLifecycleStateType GESTATING
        This is a "quantum" state: shadow is alive, but not yet alive at the same time. It probably already exists on the resource (hence exists=true). But it does not exists in the snapshot yet. Gestating shadows will not appear in resource searches. This should not be a problem for reconciliation, because they should be linked and they will be processed by reconciliation anyway.

      • LIVE

        public static final ShadowLifecycleStateType LIVE
        Normal state. Shadow exists. Everything works as expected. No quantum effects. No controversies.

      • REAPING

        public static final ShadowLifecycleStateType REAPING
        Signal to delete the resource object was sent. It is being executed.

      • CORPSE

        public static final ShadowLifecycleStateType CORPSE
        A.k.a. Schrodinger’s shadow. This is a "quantum" state: shadow is dead, but is also alive at the same time. It is probably already deleted in the resource (hence exists=false). But it still exists in the snapshot. Corpse shadows will appear in resource searches - even though is it marked as dead=true.

      • TOMBSTONE

        public static final ShadowLifecycleStateType TOMBSTONE
        Shadow is dead. Nothing remains. No resource object, no object in the snapshot. Just this stone on a grave remains. And it will also expire eventually. Tombstone shadows will not appear in resource searches - because they do not exist on the resource. But they will work with get operations. And they can be searched with noFetch.

    • Method Detail

      • values

        public static ShadowLifecycleStateType[] values()
        Returns an array containing the constants of this enum type, in the order they are declared. This method may be used to iterate over the constants as follows: 
        for (ShadowLifecycleStateType c : ShadowLifecycleStateType.values())
    System.out.println(c);
        Returns:
        an array containing the constants of this enum type, in the order they are declared

      • valueOf

        public static ShadowLifecycleStateType valueOf​(String name)
        Returns the enum constant of this type with the specified name. The string must match exactly an identifier used to declare an enum constant in this type. (Extraneous whitespace characters are not permitted.)
        Parameters:
        name - the name of the enum constant to be returned.
        Returns:
        the enum constant with the specified name
        Throws:
        IllegalArgumentException - if this enum type has no constant with the specified name
        NullPointerException - if the argument is null

      • value

        public String value()