com.codbex.kronos.parser.hdbcalculationview.ndb.datamodelhierarchy.ParentChildHierarchy Maven / Gradle / Ivy

Go to download
Show more of this group Show more artifacts with this name
Show all versions of kronos-modules-parsers-hdbcalculationview Show documentation
The newest version!
/*
 * Copyright (c) 2022 codbex or an codbex affiliate company and contributors
 *
 * All rights reserved. This program and the accompanying materials
 * are made available under the terms of the Eclipse Public License v2.0
 * which accompanies this distribution, and is available at
 * http://www.eclipse.org/legal/epl-v20.html
 *
 * SPDX-FileCopyrightText: 2022 codbex or an codbex affiliate company and contributors
 * SPDX-License-Identifier: EPL-2.0
 */
//
// This file was generated by the JavaTM Architecture for XML Binding(JAXB) Reference Implementation, v2.3.0 
// See https://javaee.github.io/jaxb-v2/ 
// Any modifications to this file will be lost upon recompilation of the source schema. 
// Generated on: 2020.11.26 at 10:54:28 AM EET 
//


package com.codbex.kronos.parser.hdbcalculationview.ndb.datamodelhierarchy;

import java.util.ArrayList;
import java.util.List;
import javax.xml.bind.annotation.XmlAccessType;
import javax.xml.bind.annotation.XmlAccessorType;
import javax.xml.bind.annotation.XmlElement;
import javax.xml.bind.annotation.XmlType;

import com.codbex.kronos.parser.hdbcalculationview.ndb.datamodeltype.Order;


/**
 * Other than for leveled hierarchies (where each level needs to be specified explicitly), a parent-child is defined by
 * exactly one parent element (for each key field in	case of compound keys). This parent(s) element describes a
 * self-referencing relationship within the master data entity and will usually be defined via an association.	Only
 * one level needs to be assigned to a parent-child hierarchy, because the levels present in the hierarchy are drawn
 * from the parent-child relationships between	members associated with the parent element. Within the same master data
 * entity one or more parent-child hierarchies could be defined. Therefore it is not sufficient to	only specify which
 * element represents the "parent" but also the corresponding "child" element needs to be defined. A simple example of a
 * Parent-Child Hierarchy is the	"Employee" master data. A Manager is again an Employee and almost every Employee is
 * assigned to a Manager
 *
 *
 * Java class for ParentChildHierarchy complex type.
 *
 * The following schema fragment specifies the expected content contained within this class.
 *
 *  * <complexType name="ParentChildHierarchy">
 *   <complexContent>
 *     <extension base="{http://www.sap.com/ndb/DataModelHierarchy.ecore}InlineHierarchy">
 *       <sequence>
 *         <element name="parentDefinition" type="{http://www.sap.com/ndb/DataModelHierarchy.ecore}ParentDefinition" maxOccurs="unbounded"/>
 *         <element name="siblingOrder" type="{http://www.sap.com/ndb/DataModelType.ecore}Order" maxOccurs="unbounded" minOccurs="0"/>
 *         <element name="timeProperties" type="{http://www.sap.com/ndb/DataModelHierarchy.ecore}HierarchyTimeProperties" minOccurs="0"/>
 *         <element name="edgeAttribute" type="{http://www.sap.com/ndb/DataModelHierarchy.ecore}EdgeAttribute" maxOccurs="unbounded" minOccurs="0"/>
 *       </sequence>
 *     </extension>
 *   </complexContent>
 * </complexType>
 * 
 */
@XmlAccessorType(XmlAccessType.FIELD)
@XmlType(name = "ParentChildHierarchy", propOrder = {
    "parentDefinition",
    "siblingOrder",
    "timeProperties",
    "edgeAttribute"
})
public class ParentChildHierarchy
    extends InlineHierarchy {

  /** The parent definition. */
  @XmlElement(required = true)
  protected List parentDefinition;
  
  /** The sibling order. */
  protected List siblingOrder;
  
  /** The time properties. */
  protected HierarchyTimeProperties timeProperties;
  
  /** The edge attribute. */
  protected List edgeAttribute;

  /**
   * Gets the value of the parentDefinition property.
   * 
   * 
   * This accessor method returns a reference to the live list,
   * not a snapshot. Therefore any modification you make to the
   * returned list will be present inside the JAXB object.
   * This is why there is not a set method for the parentDefinition property.
   * 
   * 
   * For example, to add a new item, do as follows:
   *    *    getParentDefinition().add(newItem);
   * 
   * 
   * 
   * 
   * Objects of the following type(s) are allowed in the list
   * {@link ParentDefinition }
   *
   * @return the parent definition
   */
  public List getParentDefinition() {
    if (parentDefinition == null) {
      parentDefinition = new ArrayList();
    }
    return this.parentDefinition;
  }

  /**
   * Gets the value of the siblingOrder property.
   * 
   * 
   * This accessor method returns a reference to the live list,
   * not a snapshot. Therefore any modification you make to the
   * returned list will be present inside the JAXB object.
   * This is why there is not a set method for the siblingOrder property.
   * 
   * 
   * For example, to add a new item, do as follows:
   *    *    getSiblingOrder().add(newItem);
   * 
   * 
   * 
   * 
   * Objects of the following type(s) are allowed in the list
   * {@link Order }
   *
   * @return the sibling order
   */
  public List getSiblingOrder() {
    if (siblingOrder == null) {
      siblingOrder = new ArrayList();
    }
    return this.siblingOrder;
  }

  /**
   * Gets the value of the timeProperties property.
   *
   * @return possible object is
   * {@link HierarchyTimeProperties }
   */
  public HierarchyTimeProperties getTimeProperties() {
    return timeProperties;
  }

  /**
   * Sets the value of the timeProperties property.
   *
   * @param value allowed object is
   *              {@link HierarchyTimeProperties }
   */
  public void setTimeProperties(HierarchyTimeProperties value) {
    this.timeProperties = value;
  }

  /**
   * Gets the value of the edgeAttribute property.
   * 
   * 
   * This accessor method returns a reference to the live list,
   * not a snapshot. Therefore any modification you make to the
   * returned list will be present inside the JAXB object.
   * This is why there is not a set method for the edgeAttribute property.
   * 
   * 
   * For example, to add a new item, do as follows:
   *    *    getEdgeAttribute().add(newItem);
   * 
   * 
   * 
   * 
   * Objects of the following type(s) are allowed in the list
   * {@link EdgeAttribute }
   *
   * @return the edge attribute
   */
  public List getEdgeAttribute() {
    if (edgeAttribute == null) {
      edgeAttribute = new ArrayList();
    }
    return this.edgeAttribute;
  }

}