Class SubjectType
- Direct Known Subclasses:
Subject
Java class for SubjectType complex type.
The following schema fragment specifies the expected content contained within this class.
<complexType name="SubjectType"> <complexContent> <restriction base="{http://www.w3.org/2001/XMLSchema}anyType"> <choice> <sequence> <element ref="{urn:oasis:names:tc:SAML:1.0:assertion}NameIdentifier"/> <element ref="{urn:oasis:names:tc:SAML:1.0:assertion}SubjectConfirmation" minOccurs="0"/> </sequence> <element ref="{urn:oasis:names:tc:SAML:1.0:assertion}SubjectConfirmation"/> </choice> </restriction> </complexContent> </complexType>
-
Field Summary
-
Constructor Summary
-
Method Summary
Modifier and TypeMethodDescriptionList<javax.xml.bind.JAXBElement<?>>
Gets the rest of the content model.
-
Field Details
-
-
Constructor Details
-
SubjectType
public SubjectType()
-
-
Method Details
-
getContent
Gets the rest of the content model.You are getting this "catch-all" property because of the following reason: The field name "SubjectConfirmation" is used by two different parts of a schema. See: line 101 of file:/root/xwss3.0/saml20/schemas/saml11/oasis-sstc-saml-schema-assertion-1.1.xsd line 99 of file:/root/xwss3.0/saml20/schemas/saml11/oasis-sstc-saml-schema-assertion-1.1.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 JAXB 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
<
NameIdentifierType
>
JAXBElement
<
SubjectConfirmationType
>
-