Schema "mule-ssl.xsd"
Target Namespace:
http://www.mulesoft.org/schema/mule/ssl
Defined Components:
4 global elements, 4 local elements, 3 complexTypes, 1 attribute group
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
http://www.mulesoft.org/schema/mule/ssl/3.3/mule-ssl.xsd; see XML source
Imports Schemas (4):
mule-schemadoc.xsd [src], mule-tcp.xsd [src], mule.xsd [src], xml.xsd [src]
Imported by Schema:
_mule-all-included.xsd
Annotation
The SSL transport can be used for secure socket communication using SSL or TLS. The Javadoc for this transport can be found {javadoc:mule/transport/ssl}here{javadoc}.
All Element Summary
client The client key store.
Type:
mule:tlsClientKeyStoreType
Content:
empty, 4 attributes
Defined:
locally witnin connector element; see XML source
connector Connects Mule to an SSL socket to send or receive data via the network.
Type:
anonymous complexType (extension of tcp:tcpConnectorType)
Content:
complex, 16 attributes, attr. wildcard, 11 elements
Subst.Gr:
may substitute for element mule:abstract-connector
Defined:
globally; see XML source
Includes:
definitions of 4 elements
Used:
never
endpoint
Type:
globalEndpointType
Content:
complex, 13 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:
inboundEndpointType
Content:
complex, 13 attributes, attr. wildcard, 16 elements
Subst.Gr:
may substitute for element mule:abstract-inbound-endpoint
Defined:
globally; see XML source
Used:
never
key-store The key store information, including location, key store type, and algorithm.
Type:
mule:tlsKeyStoreType
Content:
empty, 7 attributes
Defined:
locally witnin connector element; see XML source
outbound-endpoint
Type:
outboundEndpointType
Content:
complex, 13 attributes, attr. wildcard, 16 elements
Subst.Gr:
may substitute for element mule:abstract-outbound-endpoint
Defined:
globally; see XML source
Used:
never
protocol-handler Configures the global Java protocol handler by setting the java.protocol.handler.pkgs system property.
Type:
mule:tlsProtocolHandler
Content:
empty, 1 attribute
Defined:
locally witnin connector element; see XML source
server The server trust store.
Type:
mule:tlsServerTrustStoreType
Content:
empty, 8 attributes
Defined:
locally witnin connector element; see XML source
Complex Type Summary
globalEndpointType
Content:
complex, 13 attributes, attr. wildcard, 16 elements
Defined:
globally; see XML source
Used:
at 1 location
inboundEndpointType
Content:
complex, 13 attributes, attr. wildcard, 16 elements
Defined:
globally; see XML source
Used:
at 1 location
outboundEndpointType
Content:
complex, 13 attributes, attr. wildcard, 16 elements
Defined:
globally; see XML source
Used:
at 1 location
Attribute Group Summary
addressAttributes
Content:
2 attributes
Defined:
globally; see XML source
Includes:
definitions of 2 attributes
Used:
at 3 locations
XML Source
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://www.mulesoft.org/schema/mule/ssl" xmlns="http://www.mulesoft.org/schema/mule/ssl" xmlns:mule="http://www.mulesoft.org/schema/mule/core" xmlns:schemadoc="http://www.mulesoft.org/schema/mule/schemadoc" xmlns:tcp="http://www.mulesoft.org/schema/mule/tcp" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://www.w3.org/XML/1998/namespace"/>
<xsd:import namespace="http://www.mulesoft.org/schema/mule/core" schemaLocation="http://www.mulesoft.org/schema/mule/core/3.3/mule.xsd"/>
<xsd:import namespace="http://www.mulesoft.org/schema/mule/tcp" schemaLocation="http://www.mulesoft.org/schema/mule/tcp/3.3/mule-tcp.xsd"/>
<xsd:import namespace="http://www.mulesoft.org/schema/mule/schemadoc" schemaLocation="http://www.mulesoft.org/schema/mule/schemadoc/3.3/mule-schemadoc.xsd"/>
<xsd:annotation>
<xsd:documentation>
The SSL transport can be used for secure socket communication using SSL or TLS.

The Javadoc for this transport can be found {javadoc:mule/transport/ssl}here{javadoc}.
</xsd:documentation>
<xsd:appinfo>
<schemadoc:short-name>SSL</schemadoc:short-name>
<schemadoc:page-title>SSL Transport</schemadoc:page-title>
<schemadoc:transport-features dispatchEvents="true" receiveEvents="true" requestEvents="true" streaming="true" transactions="false">
<schemadoc:MEPs default="request-response" supported="one-way, request-response"/>
</schemadoc:transport-features>
</xsd:appinfo>
</xsd:annotation>
<xsd:element name="connector" substitutionGroup="mule:abstract-connector">
<xsd:annotation>
<xsd:documentation>
Connects Mule to an SSL socket to send or receive data via the network.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="tcp:tcpConnectorType">
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" name="client" type="mule:tlsClientKeyStoreType">
<xsd:annotation>
<xsd:documentation>
The client key store. SSL and TLS connections are made on behalf of an entity, which can be anonymous or identified by a certificate. This interface specifies how a keystore can be used to provide the certificates (and associated private keys) necessary for identification.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="0" name="key-store" type="mule:tlsKeyStoreType">
<xsd:annotation>
<xsd:documentation>
The key store information, including location, key store type, and algorithm.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="0" name="server" type="mule:tlsServerTrustStoreType">
<xsd:annotation>
<xsd:documentation>
The server trust store. TLS connections are made to trusted systems - the public certificates of trusted systems are stored in a keystore (called a trust store) and used to verify that the connection made to a remote system really is the expected identity.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="0" name="protocol-handler" type="mule:tlsProtocolHandler">
<xsd:annotation>
<xsd:documentation>
Configures the global Java protocol handler by setting the java.protocol.handler.pkgs system property.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="inbound-endpoint" substitutionGroup="mule:abstract-inbound-endpoint" type="inboundEndpointType"/>
<xsd:complexType name="inboundEndpointType">
<xsd:complexContent>
<xsd:extension base="mule:inboundEndpointType">
<xsd:attributeGroup ref="addressAttributes"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="outbound-endpoint" substitutionGroup="mule:abstract-outbound-endpoint" type="outboundEndpointType"/>
<xsd:complexType name="outboundEndpointType">
<xsd:complexContent>
<xsd:extension base="mule:outboundEndpointType">
<xsd:attributeGroup ref="addressAttributes"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="endpoint" substitutionGroup="mule:abstract-global-endpoint" type="globalEndpointType"/>
<xsd:complexType name="globalEndpointType">
<xsd:complexContent>
<xsd:extension base="mule:globalEndpointType">
<xsd:attributeGroup ref="addressAttributes"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:attributeGroup name="addressAttributes">
<xsd:attribute name="host" type="xsd:string"/>
<xsd:attribute name="port" type="mule:substitutablePortNumber"/>
</xsd:attributeGroup>
</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.