complexType "tns:SchemaHandlingType"
Namespace:
Content:
complex, 2 elements
Defined:
globally in common-1.xsd; see XML source
Includes:
definitions of 2 elements
Used:
XML Representation Summary
<...>
   
Content: 
tns:accountType*, tns:entitlementType*
</...>
Content Model Elements (2):
tns:accountType (in tns:schemaHandling), tns:entitlementType (in tns:schemaHandling)
All Direct / Indirect Based Elements (1):
tns:schemaHandling
Known Usage Locations
Annotation
Specification of handling details for resource schema. E.g. read-only or read-write attributes, account object classes, etc. TODO: more details This element belongs to ResourceType and should not be used elsewhere. This is a top-level element to make the implementation (JAXB marshall/unmarshall) easier.
XML Source (see within schema source)
<xsd:complexType name="SchemaHandlingType">
<xsd:annotation>
<xsd:documentation>
Specification of handling details for resource
schema. E.g. read-only or read-write attributes,
account
object
classes, etc.

TODO: more details

This element belongs to ResourceType
and should
not be used elsewhere.
This is a top-level
element to make
the implementation
(JAXB marshall/unmarshall) easier.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="accountType">
<xsd:annotation>
<xsd:documentation>
Defiens a type from the resource schema (object
class)
that can be used for creating accounts.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" ref="c:name">
<xsd:annotation>
<xsd:documentation>
Human readable name for the account object
class.
This name may be displayd in tools and GUIs
to
provide
more
pleasant user experience, as the
XML data type names may look
quite frightening.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="tns:description"/>
<xsd:element name="objectClass" type="xsd:QName">
<xsd:annotation>
<xsd:documentation>
XSD type from the resource schema (Object
Class)
that should be used for accounts on this
resource.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="attribute" type="tns:AttributeDescriptionType">
<xsd:annotation>
<xsd:documentation>
Specification of handling of an account
attribute.
This overrides annotations in the resource
schema.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="credentials">
<xsd:annotation>
<xsd:documentation>
Definition of credentials handling for this
account type.
EXPERIMENTAL. Will most likely change
later.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element default="false" minOccurs="0" name="outboundPassword" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
If true then the passowrd of the
resource
account will be automatically
changed when user
password is
changed.
EXPERIMENTAL. Will most likely change later.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="randomPasswordLength" type="xsd:integer">
<xsd:annotation>
<xsd:documentation>
If set to any value, the password will be
randomly generated when a new account
is created
and the
password cannot be
determined otherwise.
If set to zero, empty
password will be
generated. If not set
at all, the
password
attribute will not be present.
If a password can be
determined otherwise
(e.g. from User
object), the random
generation
will not be applied.
EXPERIMENTAL. Will most likely
change later.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute default="user" name="id" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Short string identifier (name) of the account
type
E.g. user, tester, guest, ...
It is supposed
to be used
in
references to this
section of XML defining account type.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute default="false" name="default" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Specifies whether this account type is the
default
account type for the resource. Only one
account
type
can be
default. Setting this flag for more
than one type is an error.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="entitlementType">
<xsd:annotation>
<xsd:documentation>
Type of entitlements such as groups, roles
entitlements, organizatrions, etc.

Not yet fully
figured out.
Please
ignore for now.

TODO
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" ref="c:name">
<xsd:annotation>
<xsd:documentation>
Human readable name for
the object class.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="objectClass" type="xsd:QName">
<xsd:annotation>
<xsd:documentation>
TODO
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="assignmentProperty">
<xsd:annotation>
<xsd:documentation>
TODO
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:attribute name="ref" type="xsd:QName"/>
<xsd:attribute default="1" name="minOccurs" type="xsd:string" use="optional"/>
<xsd:attribute default="1" name="maxOccurs" type="xsd:string" use="optional"/>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
TODO
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
Content Element Detail (all declarations; 2/2)
tns:accountType
Type:
anonymous complexType, complex content
Defined:
locally within (this) tns:SchemaHandlingType complexType
Defiens a type from the resource schema (object class) that can be used for creating accounts.
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="accountType">
<xsd:annotation>
<xsd:documentation>
Defiens a type from the resource schema (object
class)
that can be used for creating accounts.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" ref="c:name">
<xsd:annotation>
<xsd:documentation>
Human readable name for the account object
class.
This name may be displayd in tools and GUIs
to
provide
more
pleasant user experience, as the
XML data type names may look
quite frightening.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="tns:description"/>
<xsd:element name="objectClass" type="xsd:QName">
<xsd:annotation>
<xsd:documentation>
XSD type from the resource schema (Object
Class)
that should be used for accounts on this
resource.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="attribute" type="tns:AttributeDescriptionType">
<xsd:annotation>
<xsd:documentation>
Specification of handling of an account
attribute.
This overrides annotations in the resource
schema.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="credentials">
<xsd:annotation>
<xsd:documentation>
Definition of credentials handling for this
account type.
EXPERIMENTAL. Will most likely change
later.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element default="false" minOccurs="0" name="outboundPassword" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
If true then the passowrd of the
resource
account will be automatically
changed when user
password is
changed.
EXPERIMENTAL. Will most likely change later.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="randomPasswordLength" type="xsd:integer">
<xsd:annotation>
<xsd:documentation>
If set to any value, the password will be
randomly generated when a new account
is created
and the
password cannot be
determined otherwise.
If set to zero, empty
password will be
generated. If not set
at all, the
password
attribute will not be present.
If a password can be
determined otherwise
(e.g. from User
object), the random
generation
will not be applied.
EXPERIMENTAL. Will most likely
change later.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute default="user" name="id" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Short string identifier (name) of the account
type
E.g. user, tester, guest, ...
It is supposed
to be used
in
references to this
section of XML defining account type.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute default="false" name="default" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Specifies whether this account type is the
default
account type for the resource. Only one
account
type
can be
default. Setting this flag for more
than one type is an error.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>

tns:entitlementType
Type:
anonymous complexType, complex content
Defined:
locally within (this) tns:SchemaHandlingType complexType
Type of entitlements such as groups, roles entitlements, organizatrions, etc. Not yet fully figured out. Please ignore for now. TODO
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="entitlementType">
<xsd:annotation>
<xsd:documentation>
Type of entitlements such as groups, roles
entitlements, organizatrions, etc.

Not yet fully
figured out.
Please
ignore for now.

TODO
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" ref="c:name">
<xsd:annotation>
<xsd:documentation>
Human readable name for
the object class.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="objectClass" type="xsd:QName">
<xsd:annotation>
<xsd:documentation>
TODO
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="assignmentProperty">
<xsd:annotation>
<xsd:documentation>
TODO
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:attribute name="ref" type="xsd:QName"/>
<xsd:attribute default="1" name="minOccurs" type="xsd:string" use="optional"/>
<xsd:attribute default="1" name="maxOccurs" type="xsd:string" use="optional"/>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="id" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
TODO
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
</xsd:element>

This XML schema documentation has been generated with DocFlex/XML RE 1.8.5 using DocFlex/XML XSDDoc 2.5.0 template set.
DocFlex/XML RE is a reduced edition of DocFlex/XML, which is a tool for programming and running highly sophisticated documentation and reports generators by the data obtained from any kind of XML files. The actual doc-generators are implemented in the form of special templates that are designed visually using a high-quality Template Designer GUI basing on the XML schema (or DTD) files describing the data source XML.
DocFlex/XML XSDDoc is a commercial template application of DocFlex/XML that implements a high-quality XML Schema documentation generator with simultaneous support of framed multi-file HTML, single-file HTML and RTF output formats. (More formats are planned in the future).
A commercial license for "DocFlex/XML XSDDoc" will allow you:
  • To configure the generated documentation so much as you want. Thanks to our template technology, it was possible to support > 400 template parameters, which work the same as "options" of ordinary doc-generators. The parameters are organized in nested groups, which form a parameter tree. Most of them have their default values calculated dynamically from a few primary parameters. So, you'll never need to specify all of them. That will give you swift and effective control over the generated content!
  • To use certain features disabled in the free mode (such as the full documenting of substitution groups).
  • To select only the initial, imported, included, redefined XML schemas to be documented or only those directly specified by name.
  • To include only XML schema components specified by name.
  • To document local element components both globally and locally (similar to attributes).
  • To allow/suppress unification of local elements by type.
  • To enable/disable reproducing of namespace prefixes.
  • To use PlainDoc.tpl main template to generate all the XML schema documentation in a signle-file form as both HTML and incredible quality RTF output.
  • To format your annotations with XHTML tags and reproduce that formatting both in HTML and RTF output.
  • To insert images in your annotations using XHTML <img> tags (supported both in HTML and RTF output).
  • To remove this very advertisement text!
Once having only such a license, you will be able to run the fully-featured XML schema documentation generator both with DocFlex/XML (Full Edition) and with DocFlex/XML RE, which is a reduced free edition containing only the template interpretor / output generator. No other licenses will be required!
But this is not all. In addition to it, a commercial license for "DocFlex/XML SDK" will allow you to modify the XSDDoc templates themselves as much as you want. You will be able to achieve whatever was impossible to do with the template parameters only. And, of course, you could develop any template applications by your own!
Please note that by purchasing a license for this software, you not only acquire a useful tool, you will also make an important investment in its future development, the results of which you could enjoy later by yourself. Every single your purchase matters and makes a difference for us!
To purchase a license, please follow this link: http://www.filigris.com/shop/