complexType "inboundEndpointType"
Namespace:
Content:
complex, 14 attributes, 12 elements
Defined:
globally in mule-imap.xsd; see XML source
Used:
Content Model Diagram
XML Representation Summary
<...
    name
 = 
(xsd:string | xsd:NMTOKEN)
    mimeType
 = 
xsd:string
    responseTimeout
 = 
(xsd:string | xsd:int)
    encoding
 = 
xsd:string
    connector-ref
 = 
xsd:string
    transformer-refs
 = 
xsd:NMTOKENS
    responseTransformer-refs
 = 
xsd:NMTOKENS
    disableTransportTransformer
 = 
(xsd:string | xsd:boolean)
    ref
 = 
xsd:string
    address
 = 
xsd:string
    user
 = 
xsd:string
    password
 = 
xsd:string
    host
 = 
xsd:string
    port
 = 
(xsd:string | xsd:int)
    >
   
Content: 
(abstract-transformer | abstract-filter | abstract-security-filter | abstract-intercepting-message-processor | processor | custom-processor)*, response?, abstract-transaction?, abstract-retry-policy?, abstract-multi-transaction?, property*, properties?
</...>
Content Model Elements (12):
All Direct / Indirect Based Elements (1):
Known Usage Locations
Type Definition Detail
Type Derivation Tree
      inboundEndpointType
XML Source (see within schema source)
<xsd:complexType name="inboundEndpointType">
<xsd:complexContent>
<!--
The only valid exchange-pattern is one-way which is the default. No need to make
the exchange-pattern attribute configurable.
-->
<xsd:attributeGroup ref="email:addressAttributes"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>

XML schema documentation generated with DocFlex/XML SDK 1.8.1b6 using DocFlex/XML XSDDoc 2.2.1 template set. All content model diagrams generated by Altova XMLSpy via DocFlex/XML XMLSpy Integration.