complexType "tns:ResourceObjectShadowChangeDescriptionType"
Namespace:
Content:
complex, 4 elements
Defined:
globally in common-1.xsd; see XML source
Includes:
definitions of 4 elements
Used:
never
XML Representation Summary
<...>
   
Content: 
tns:objectChange, tns:sourceChannel, tns:shadow, tns:resource
</...>
Content Model Elements (4):
tns:objectChange (type tns:ObjectChangeType), tns:resource (type tns:ResourceType), tns:shadow (type tns:ResourceObjectShadowType), tns:sourceChannel (type xsd:anyURI)
Annotation
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.
XML Source (see within schema source)
<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: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>
<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>
<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>
<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>
</xsd:sequence>
</xsd:complexType>
Content Element Detail (all declarations; 4/4)
tns:objectChange
Type:
tns:ObjectChangeType, empty content
Defined:
Description of changes that happened to an resource object shadow.
XML Source (see within schema source)
<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>

tns:resource
Type:
tns:ResourceType, complex content
Defined:
Resource that was the origin of the change.
XML Source (see within schema source)
<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>

tns:shadow
Type:
Defined:
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).
XML Source (see within schema source)
<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>

tns:sourceChannel
Type:
xsd:anyURI, simple content
Defined:
Definition of source channel (e.g. synchronization, reconciliation, discovery, ...) Should in fact be QName. But OpenESB has problems with QNames.
XML Source (see within schema source)
<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:
  • 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/