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

Class LookupTableType

  • All Implemented Interfaces:
    Containerable, JaxbVisitable, Objectable, DebugDumpable, Serializable, Cloneable
    public class LookupTableType
extends AssignmentHolderType
implements Serializable, Cloneable
     <?xml version="1.0" encoding="UTF-8"?><p xmlns:a="http://prism.evolveum.com/xml/ns/public/annotation-3" xmlns:c="http://midpoint.evolveum.com/xml/ns/public/common/common-3" xmlns:icfs="http://midpoint.evolveum.com/xml/ns/public/connector/icf-1/resource-schema-3" xmlns:jaxb="http://java.sun.com/xml/ns/jaxb" xmlns:q="http://prism.evolveum.com/xml/ns/public/query-3" xmlns:s="http://midpoint.evolveum.com/xml/ns/public/model/scripting-3" xmlns:t="http://prism.evolveum.com/xml/ns/public/types-3" xmlns:tns="http://midpoint.evolveum.com/xml/ns/public/common/common-3" xmlns:xjc="http://java.sun.com/xml/ns/jaxb/xjc" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                     An object that represents lookup table. The lookup table can be used for two purposes:
                     value enumerations (e.g. for GUI or validation) and value mapping (translation).
                     The same lookup table can serve both purposes at the same time.
                 </p>
 
     <?xml version="1.0" encoding="UTF-8"?><p xmlns:a="http://prism.evolveum.com/xml/ns/public/annotation-3" xmlns:c="http://midpoint.evolveum.com/xml/ns/public/common/common-3" xmlns:icfs="http://midpoint.evolveum.com/xml/ns/public/connector/icf-1/resource-schema-3" xmlns:jaxb="http://java.sun.com/xml/ns/jaxb" xmlns:q="http://prism.evolveum.com/xml/ns/public/query-3" xmlns:s="http://midpoint.evolveum.com/xml/ns/public/model/scripting-3" xmlns:t="http://prism.evolveum.com/xml/ns/public/types-3" xmlns:tns="http://midpoint.evolveum.com/xml/ns/public/common/common-3" xmlns:xjc="http://java.sun.com/xml/ns/jaxb/xjc" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                     The content of the lookup table can be used as enumeration. E.g. the labels for each
                     table row can be displayed in the user interface. When a particular label is selected then
                     the associated key will be stored. Similar approach can be used for validation, e.g. when only
                     a selected set of values is legal for a certain property. In this case the "key" and "label"
                     columns are used.
                 </p>
 
     <?xml version="1.0" encoding="UTF-8"?><p xmlns:a="http://prism.evolveum.com/xml/ns/public/annotation-3" xmlns:c="http://midpoint.evolveum.com/xml/ns/public/common/common-3" xmlns:icfs="http://midpoint.evolveum.com/xml/ns/public/connector/icf-1/resource-schema-3" xmlns:jaxb="http://java.sun.com/xml/ns/jaxb" xmlns:q="http://prism.evolveum.com/xml/ns/public/query-3" xmlns:s="http://midpoint.evolveum.com/xml/ns/public/model/scripting-3" xmlns:t="http://prism.evolveum.com/xml/ns/public/types-3" xmlns:tns="http://midpoint.evolveum.com/xml/ns/public/common/common-3" xmlns:xjc="http://java.sun.com/xml/ns/jaxb/xjc" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                     The content of the lookup table can also be used for value mapping. E.g. in cases when
                     input value needs to be mapped to the output value. In this case the "key" and "value"
                     columns are used.
                 </p>
 
     <?xml version="1.0" encoding="UTF-8"?><p xmlns:a="http://prism.evolveum.com/xml/ns/public/annotation-3" xmlns:c="http://midpoint.evolveum.com/xml/ns/public/common/common-3" xmlns:icfs="http://midpoint.evolveum.com/xml/ns/public/connector/icf-1/resource-schema-3" xmlns:jaxb="http://java.sun.com/xml/ns/jaxb" xmlns:q="http://prism.evolveum.com/xml/ns/public/query-3" xmlns:s="http://midpoint.evolveum.com/xml/ns/public/model/scripting-3" xmlns:t="http://prism.evolveum.com/xml/ns/public/types-3" xmlns:tns="http://midpoint.evolveum.com/xml/ns/public/common/common-3" xmlns:xjc="http://java.sun.com/xml/ns/jaxb/xjc" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                     Even though the lookup table is represented as a prism object, it is designed to be
                     stored and queried efficiently. Therefore the contents of the lookup table will
                     be stored in a specialized table tuned for this purpose. This data type is not
                     designed to be used with the usual midPoint query mechanism (e.g. searchObjects operation).
                     Specialized operations are used to efficiently query the lookup tables. The prism
                     representation (e.g. XML) of the lookup tables is used only for backup, restore, migrations,
                     upgrades and similar purposes.
                 </p>

    Java class for LookupTableType complex type.

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

     <complexType name="LookupTableType">
   <complexContent>
     <extension base="{http://midpoint.evolveum.com/xml/ns/public/common/common-3}AssignmentHolderType">
       <sequence>
         <element name="row" type="{http://midpoint.evolveum.com/xml/ns/public/common/common-3}LookupTableRowType" maxOccurs="unbounded" minOccurs="0"/>
       </sequence>
     </extension>
   </complexContent>
 </complexType>
    See Also:
    Serialized Form