Class SignersDocumentType

java.lang.Object
eu.europa.esig.validationreport.jaxb.SignersDocumentType
All Implemented Interfaces:
Serializable
public class SignersDocumentType extends Object implements Serializable

Java class for SignersDocumentType complex type.

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

<complexType name="SignersDocumentType">
  <complexContent>
    <restriction base="{http://www.w3.org/2001/XMLSchema}anyType">
      <sequence>
        <choice>
          <sequence>
            <element name="DigestAlgAndValue" type="{http://uri.etsi.org/01903/v1.3.2#}DigestAlgAndValueType"/>
            <element name="SignersDocumentRepresentation" type="{http://uri.etsi.org/19102/v1.4.1#}VOReferenceType" minOccurs="0"/>
          </sequence>
          <element name="SignersDocumentRepresentation" type="{http://uri.etsi.org/19102/v1.4.1#}VOReferenceType"/>
        </choice>
        <element name="SignersDocumentRef" type="{http://uri.etsi.org/19102/v1.4.1#}VOReferenceType" minOccurs="0"/>
      </sequence>
    </restriction>
  </complexContent>
</complexType>
See Also:

  • Field Details

    • content

      protected List<jakarta.xml.bind.JAXBElement<?>> content

  • Constructor Details

    • SignersDocumentType

      public SignersDocumentType()

  • Method Details

    • getContent

      public List<jakarta.xml.bind.JAXBElement<?>> getContent()
      Gets the rest of the content model.

      You are getting this "catch-all" property because of the following reason: The field name "SignersDocumentRepresentation" is used by two different parts of a schema. See: line 141 of file:/C:/Users/AleksandrBeliakov/BitBucket/dss/specs-validation-report/src/main/resources/xsd/1910202xmlSchema.xsd line 139 of file:/C:/Users/AleksandrBeliakov/BitBucket/dss/specs-validation-report/src/main/resources/xsd/1910202xmlSchema.xsd

      To get rid of this property, apply a property customization to one of both of the following declarations to change their names: Gets the value of the content 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 content property.

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

         getContent().add(newItem);

      Objects of the following type(s) are allowed in the list JAXBElement<VOReferenceType> JAXBElement<VOReferenceType> JAXBElement<DigestAlgAndValueType>