Schema "mule-pop3s.xsd"
Target Namespace:
http://www.mulesoft.org/schema/mule/pop3s
Defined Components:
global elements, 2 local elements, 3 complexTypes
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
http://www.mulesoft.org/schema/mule/pop3s/3.3/mule-pop3s.xsd; see XML source
Imports Schemas (5):
mule-email.xsd [src], mule-pop3.xsd [src], mule-schemadoc.xsd [src], mule.xsd [src], xml.xsd [src]
Imported by Schema:
_mule-all-included.xsd
Annotation
The POP3S transport is similar to the [POP3 Transport] but uses secure connections over SSL/TLS.
All Element Summary
connector
Type:
Content:
complex, 11 attributes, attr. wildcard, 8 elements
Subst.Gr:
may substitute for element mule:abstract-connector
Defined:
globally; see XML source
Used:
never
endpoint
Type:
Content:
complex, 14 attributes, attr. wildcard, 16 elements
Subst.Gr:
may substitute for element mule:abstract-global-endpoint
Defined:
globally; see XML source
Used:
never
inbound-endpoint
Type:
Content:
complex, 14 attributes, attr. wildcard, 16 elements
Subst.Gr:
may substitute for element mule:abstract-inbound-endpoint
Defined:
globally; see XML source
Used:
never
tls-client
Type:
Content:
empty, 4 attributes
Defined:
locally witnin pop3sConnectorType complexType; see XML source
tls-trust-store
Type:
Content:
empty, 2 attributes
Defined:
locally witnin pop3sConnectorType complexType; see XML source
Complex Type Summary
Content:
complex, 14 attributes, attr. wildcard, 16 elements
Defined:
globally; see XML source
Used:
Content:
complex, 14 attributes, attr. wildcard, 16 elements
Defined:
globally; see XML source
Used:
Content:
complex, 11 attributes, attr. wildcard, 8 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
XML Source
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://www.mulesoft.org/schema/mule/pop3s" xmlns="http://www.mulesoft.org/schema/mule/pop3s" xmlns:email="http://www.mulesoft.org/schema/mule/email" xmlns:mule="http://www.mulesoft.org/schema/mule/core" xmlns:pop3="http://www.mulesoft.org/schema/mule/pop3" xmlns:schemadoc="http://www.mulesoft.org/schema/mule/schemadoc" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://www.w3.org/XML/1998/namespace"/>
<xsd:annotation>
<xsd:documentation>
The POP3S transport is similar to the [POP3 Transport] but uses secure connections over SSL/TLS.
</xsd:documentation>
<xsd:appinfo>
<schemadoc:short-name>POP3S</schemadoc:short-name>
<schemadoc:page-title>POP3S Transport</schemadoc:page-title>
<schemadoc:artifact-name>email</schemadoc:artifact-name>
<schemadoc:transport-features dispatchEvents="false" receiveEvents="true" requestEvents="true" streaming="false" transactions="false">
<schemadoc:MEPs default="one-way" supported="one-way"/>
</schemadoc:transport-features>
</xsd:appinfo>
</xsd:annotation>
<xsd:element name="connector" substitutionGroup="mule:abstract-connector" type="pop3sConnectorType"/>
<xsd:complexType name="pop3sConnectorType">
<xsd:complexContent>
<xsd:extension base="pop3:pop3ConnectorType">
<xsd:sequence maxOccurs="1" minOccurs="0">
<xsd:element name="tls-client" type="mule:tlsClientKeyStoreType"/>
<xsd:element name="tls-trust-store" type="mule:tlsTrustStoreType"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="inbound-endpoint" substitutionGroup="mule:abstract-inbound-endpoint" type="inboundEndpointType"/>
<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>
<xsd:element name="endpoint" substitutionGroup="mule:abstract-global-endpoint" type="globalEndpointType"/>
<xsd:complexType name="globalEndpointType">
<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>
</xsd:schema>

XML schema documentation generated with DocFlex/XML RE 1.8.5 using DocFlex/XML XSDDoc 2.5.0 template set. All content model diagrams generated by Altova XMLSpy via DocFlex/XML XMLSpy Integration.