element <message> (local)
Namespace:
Type:
Content:
complex, 3 attributes, 2 elements
Defined:
locally within myInboxType complexType in myInbox.xsd; see XML source
XML Representation Summary
<message
   
 = 
xsd:nonNegativeInteger
 = 
xsd:hexBinary
 = 
xsd:string
   
>
   
Content: 
</message>
Content model elements (2):
messageContent (in message in myInbox), messageStatus (in message in myInbox)
Included in content model of elements (1):
myInbox
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="message" type="messageType"/>
Attribute Detail (all declarations; 3/3)
changeNumber
Type:
Use:
required
Defined:
XML Source (see within schema source)
<xsd:attribute name="changeNumber" type="changeNumberType" use="required"/>

creator
Type:
Use:
required
Defined:
XML Source (see within schema source)
<xsd:attribute name="creator" type="creatorType" use="required"/>

id
Type:
Use:
required
Defined:
XML Source (see within schema source)
<xsd:attribute name="id" type="idType" use="required"/>
Content Element Detail (all declarations; 2/2)
messageContent
Type:
messageContentType, complex content
Defined:
locally within messageType complexType
This element defines the content of the message. This data changes rarely in a normal application.
XML Source (see within schema source)
<xsd:element name="messageContent" type="messageContentType">
<xsd:annotation>
<xsd:documentation>
This element defines the content of the message. This data changes rarely in a normal application.
</xsd:documentation>
</xsd:annotation>
</xsd:element>

messageStatus
Type:
messageStatusType, complex content
Defined:
locally within messageType complexType
This element defines the status of the email and frequently changes. Caching clients should take advantage of this when deciding which part of the message to change
XML Source (see within schema source)
<xsd:element name="messageStatus" type="messageStatusType">
<xsd:annotation>
<xsd:documentation>
This element defines the status of the email and frequently changes. Caching clients should take
advantage of this when deciding which part of the message to change
</xsd:documentation>
</xsd:annotation>
</xsd:element>