Namespace: |
|
Type: |
anonymous complexType |
Content: |
complex, 2 elements |
Defined: |
globally in myInbox.xsd; see XML source |
Includes: |
definitions of 2 elements |
Used: |
never |
XML Representation Summary |
|||||
<sendMessageRequest> |
|||||
|
|||||
</sendMessageRequest> |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
This method is used to send a message from myInbox. It takes either a pointer to a draft
</xsd:documentation>
message to send, or a raw message that represents a full RFC2822/Mime message. This method is accessed using a request message, and in response may generate a domain-specific response message, or may generate a SOAP fault message. The types used in these messages are fully specified in the services base schema document referenced above. The following sample document fragments illustrate the structure and meaning of the elements and attributes in the request and response messages. <xsd:complexType>
<xsd:sequence>
</xsd:complexType>
<!-- TODO: make this a choice -->
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element is used to identify an existing draft to send.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element is used to specify a raw message to send.
</xsd:documentation>
</xsd:element>
|
Type: |
draftMessagePointerType, complex content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
This element is used to identify an existing draft to send.
</xsd:documentation>
</xsd:element>
|
Type: |
rawMessageType, complex content |
Defined: |
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
This element is used to specify a raw message to send.
</xsd:documentation>
</xsd:element>
|