Namespace: |
|
Content: |
complex, 4 elements |
Defined: |
globally in common-1.xsd; see XML source |
Includes: |
definitions of 4 elements |
Used: |
never |
XML Representation Summary |
|||||
<...> | |||||
|
|||||
</...> |
<xsd:complexType name="ResourceObjectShadowChangeDescriptionType"> <xsd:annotation> <xsd:documentation> Describes a change of a specific resource object together with definitions of the source. Note: This is quite an atrificial structure. In fact it should be splint into WSDL message parts instead one XSD type. But the ObjectChangeType is polymorphic and OpenESB has problems with such types if placed directly into message parts. </xsd:documentation> </xsd:annotation> <xsd:sequence> <xsd:annotation> <xsd:documentation> Description of changes that happened to an resource object shadow. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation> Definition of source channel (e.g. synchronization, reconciliation, discovery, ...) Should in fact be QName. But OpenESB has problems with QNames. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation> Resource object shadow as seen by the component before the change, if possible. This object is mandatory. In some cases (e.g. addition) the object may not exist before the change. In such a case the caller is reponsible to create such object in the repository before calling this operation (see the note before). Even thought this object is mandatory, it may not be complete. The content of this object depends on how the change was detected, configuration of a calling component and so on. On the very minimum, the shadow object must contain: * OID * Identifiers necessary to locate the associated resource object on the resource. Note: This is actually the shadow object that was stored in the repository at the time the change was detected (or created at that moment). Note: This was orginally defined as an object before the change and it was option. Such definition does not allow some operations, such as create a user and link account (because the objectChange does not have OID and therefore cannot be linked to). </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:annotation> <xsd:documentation> Resource that was the origin of the change. </xsd:documentation> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:complexType> |
Type: |
tns:ObjectChangeType, empty content |
Defined: |
<xsd:element name="objectChange" type="tns:ObjectChangeType"> <xsd:annotation> <xsd:documentation> Description of changes that happened to an resource object shadow. </xsd:documentation> </xsd:annotation> </xsd:element> |
Type: |
tns:ResourceType, complex content |
Defined: |
<xsd:element name="resource" type="tns:ResourceType"> <xsd:annotation> <xsd:documentation> Resource that was the origin of the change. </xsd:documentation> </xsd:annotation> </xsd:element> |
Type: |
tns:ResourceObjectShadowType, complex content |
Defined: |
<xsd:element name="shadow" type="tns:ResourceObjectShadowType"> <xsd:annotation> <xsd:documentation> Resource object shadow as seen by the component before the change, if possible. This object is mandatory. In some cases (e.g. addition) the object may not exist before the change. In such a case the caller is reponsible to create such object in the repository before calling this operation (see the note before). Even thought this object is mandatory, it may not be complete. The content of this object depends on how the change was detected, configuration of a calling component and so on. On the very minimum, the shadow object must contain: * OID * Identifiers necessary to locate the associated resource object on the resource. Note: This is actually the shadow object that was stored in the repository at the time the change was detected (or created at that moment). Note: This was orginally defined as an object before the change and it was option. Such definition does not allow some operations, such as create a user and link account (because the objectChange does not have OID and therefore cannot be linked to). </xsd:documentation> </xsd:annotation> </xsd:element> |
Type: |
xsd:anyURI, simple content |
Defined: |
<xsd:element name="sourceChannel" type="xsd:anyURI"> <xsd:annotation> <xsd:documentation> Definition of source channel (e.g. synchronization, reconciliation, discovery, ...) Should in fact be QName. But OpenESB has problems with QNames. </xsd:documentation> </xsd:annotation> </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:
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/ |