Module com.foursoft.harness.vec.v113
Package com.foursoft.harness.vec.v113

Class VecCompatibilityStatement

java.lang.Object
com.foursoft.harness.vec.v113.VecExtendableElement
com.foursoft.harness.vec.v113.VecCompatibilityStatement
All Implemented Interfaces:
Identifiable, ModifiableIdentifiable, HasCustomProperties<VecCustomProperty>, Visitable, Serializable
public class VecCompatibilityStatement extends VecExtendableElement implements Serializable, Visitable

A CompatibilityStatement is used to express compatibility between parts. This can be either compatibility for contacting (terminals, wires, seals, a.s.o.) or for plugging (connector housings, slots, a.s.o.).

A CompatibilityStatement can be used to explicitly express compatibility (hasCompatibility = true) or to express incompatibility / negation (hasCompatibility = false).

The CompatibilityStatement is stated by referencing the corresponding specifications. In the concrete implementation this mechanisms allows three different variants to express compatibility.

In the first variant the CompatibilityStatement references specifications that are not directly related to a concrete PartVersion (association in the super-class PartOrUsageRelatedSpecification). In this case the attributes of the specification represent a search pattern for searching compatible parts in a component library.

In the second variant the CompatibilityStatement references the same specifications that are used to specify the component attributes of a PartVersion. This would be equivalent to an explicit mapping compatible PartVersions.

In the third variant the CompatibilityStatement references specifications that do not have any attributes at all. These specifications are normally defined in the same document that defines the CompatibilitySpecification. Such a specification can group multiple PartVersion by referencing them. This is possible, because the VEC makes no restriction on the number of specifications that can be defined for single PartVersion.

Java class for CompatibilityStatement complex type.

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


 <complexType name="CompatibilityStatement">
   <complexContent>
     <extension base="{http://www.prostep.org/ecad-if/2011/vec}ExtendableElement">
       <sequence>
         <element name="HasCompatibility" type="{http://www.w3.org/2001/XMLSchema}boolean"/>
         <element name="Cavity" type="{http://www.w3.org/2001/XMLSchema}IDREFS" minOccurs="0"/>
         <element name="CavityPlugSpecification" type="{http://www.w3.org/2001/XMLSchema}IDREFS" minOccurs="0"/>
         <element name="CavitySealSpecification" type="{http://www.w3.org/2001/XMLSchema}IDREFS" minOccurs="0"/>
         <element name="CavitySpecification" type="{http://www.w3.org/2001/XMLSchema}IDREFS" minOccurs="0"/>
         <element name="ConnectorHousingSpecification" type="{http://www.w3.org/2001/XMLSchema}IDREFS" minOccurs="0"/>
         <element name="Slot" type="{http://www.w3.org/2001/XMLSchema}IDREFS" minOccurs="0"/>
         <element name="TerminalSpecification" type="{http://www.w3.org/2001/XMLSchema}IDREFS" minOccurs="0"/>
         <element name="WireSpecification" type="{http://www.w3.org/2001/XMLSchema}IDREFS" minOccurs="0"/>
       </sequence>
     </extension>
   </complexContent>
 </complexType>
See Also:

  • Field Details

    • hasCompatibility

      protected boolean hasCompatibility

      If true the CompatibilityStatement states compatibility, otherwise incompatibility.

    • cavity

      protected List<VecCavity> cavity

      References explicit cavities for which the compatibility statement is stated.

    • cavityPlugSpecification

      protected List<VecCavityPlugSpecification> cavityPlugSpecification

      References the CavityPlugSpecifications for which the compatibility statement is stated.

    • cavitySealSpecification

      protected List<VecCavitySealSpecification> cavitySealSpecification

      References the CavitySealSpecifications for which the compatibility statement is stated.

    • cavitySpecification

      protected List<VecCavitySpecification> cavitySpecification

      References the CavitySpecifications for which the compatibility statement is stated.

    • connectorHousingSpecification

      protected List<VecConnectorHousingSpecification> connectorHousingSpecification

      References the ConnectorHousingSpecifications for which the compatibility statement is stated.

    • slot

      protected List<VecAbstractSlot> slot

      References explicit Slots for which the compatibility statement is stated.

    • terminalSpecification

      protected List<VecTerminalSpecification> terminalSpecification

      References the TerminalSpecifications for which the compatibility statement is stated.

    • wireSpecification

      protected List<VecWireSpecification> wireSpecification

      References the WireSpecifications for which the compatibility statement is stated.

  • Constructor Details

    • VecCompatibilityStatement

      public VecCompatibilityStatement()

  • Method Details

    • isHasCompatibility

      public boolean isHasCompatibility()
      Gets the value of the hasCompatibility property.

      If true the CompatibilityStatement states compatibility, otherwise incompatibility.

    • setHasCompatibility

      public void setHasCompatibility(boolean value)
      Sets the value of the hasCompatibility property.
      See Also:

    • getCavity

      public List<VecCavity> getCavity()
      Gets the value of the cavity 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 Jakarta XML Binding object. This is why there is not a set method for the cavity property.

      For example, to add a new item, do as follows: 

          getCavity().add(newItem);

      Objects of the following type(s) are allowed in the list Object

      References explicit cavities for which the compatibility statement is stated.

    • getCavityPlugSpecification

      public List<VecCavityPlugSpecification> getCavityPlugSpecification()
      Gets the value of the cavityPlugSpecification 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 Jakarta XML Binding object. This is why there is not a set method for the cavityPlugSpecification property.

      For example, to add a new item, do as follows: 

          getCavityPlugSpecification().add(newItem);

      Objects of the following type(s) are allowed in the list Object

      References the CavityPlugSpecifications for which the compatibility statement is stated.

    • getCavitySealSpecification

      public List<VecCavitySealSpecification> getCavitySealSpecification()
      Gets the value of the cavitySealSpecification 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 Jakarta XML Binding object. This is why there is not a set method for the cavitySealSpecification property.

      For example, to add a new item, do as follows: 

          getCavitySealSpecification().add(newItem);

      Objects of the following type(s) are allowed in the list Object

      References the CavitySealSpecifications for which the compatibility statement is stated.

    • getCavitySpecification

      public List<VecCavitySpecification> getCavitySpecification()
      Gets the value of the cavitySpecification 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 Jakarta XML Binding object. This is why there is not a set method for the cavitySpecification property.

      For example, to add a new item, do as follows: 

          getCavitySpecification().add(newItem);

      Objects of the following type(s) are allowed in the list Object

      References the CavitySpecifications for which the compatibility statement is stated.

    • getConnectorHousingSpecification

      public List<VecConnectorHousingSpecification> getConnectorHousingSpecification()
      Gets the value of the connectorHousingSpecification 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 Jakarta XML Binding object. This is why there is not a set method for the connectorHousingSpecification property.

      For example, to add a new item, do as follows: 

          getConnectorHousingSpecification().add(newItem);

      Objects of the following type(s) are allowed in the list Object

      References the ConnectorHousingSpecifications for which the compatibility statement is stated.

    • getSlot

      public List<VecAbstractSlot> getSlot()
      Gets the value of the slot 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 Jakarta XML Binding object. This is why there is not a set method for the slot property.

      For example, to add a new item, do as follows: 

          getSlot().add(newItem);

      Objects of the following type(s) are allowed in the list Object

      References explicit Slots for which the compatibility statement is stated.

    • getTerminalSpecification

      public List<VecTerminalSpecification> getTerminalSpecification()
      Gets the value of the terminalSpecification 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 Jakarta XML Binding object. This is why there is not a set method for the terminalSpecification property.

      For example, to add a new item, do as follows: 

          getTerminalSpecification().add(newItem);

      Objects of the following type(s) are allowed in the list Object

      References the TerminalSpecifications for which the compatibility statement is stated.

    • getWireSpecification

      public List<VecWireSpecification> getWireSpecification()
      Gets the value of the wireSpecification 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 Jakarta XML Binding object. This is why there is not a set method for the wireSpecification property.

      For example, to add a new item, do as follows: 

          getWireSpecification().add(newItem);

      Objects of the following type(s) are allowed in the list Object

      References the WireSpecifications for which the compatibility statement is stated.

    • getParentCompatibilitySpecification

      public VecCompatibilitySpecification getParentCompatibilitySpecification()
      Gets a reference to the parent of this object in the XML DOM Tree. If this class can have different parents in DOM, this property is initialized with the parent, if the parent is a VecCompatibilitySpecification otherwise it will be null.
      Warning!: This is a readonly property! It has to be initialized during the unmarshalling process by the ExtendedUnmarshaller.
      This property is consistent to the state of object model at the time of unmarshalling. It does not reflect any changes done in the object model after the unmarshalling.
      This property has no effect when the object is marshalled to xml.

    • accept

      public <R, E extends Throwable> R accept(Visitor<R,E> aVisitor) throws E
      Specified by:
      accept in interface Visitable
      Throws:
      E extends Throwable