Schema "mule-jetty-ssl.xsd"
Target Namespace:
http://www.mulesoft.org/schema/mule/jetty-ssl
Defined Components:
3 global elements, 5 local elements, 3 complexTypes
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
http://www.mulesoft.org/schema/mule/jetty-ssl/3.3/mule-jetty-ssl.xsd; see XML source
Imports Schemas (5):
mule-http.xsd [src], mule-jetty.xsd [src], mule-schemadoc.xsd [src], mule.xsd [src], xml.xsd [src]
Imported by Schema:
_mule-all-included.xsd
Annotation
The Jetty HTTPS transport provides support for exposing services over HTTPS by embedding a light-weight Jetty server. You can only define inbound endpoints with this transport.
All Element Summary
connector Allows Mule to expose Mule Services over HTTPS using a Jetty HTTP server.
Type:
jettySslConnectorType
Content:
complex, 2 attributes, attr. wildcard, 6 elements
Subst.Gr:
may substitute for element mule:abstract-connector
Defined:
globally; see XML source
Used:
never
endpoint Allows users to configure a global Jetty HTTPS endpoint.
Type:
globalEndpointType
Content:
complex, 20 attributes, attr. wildcard, 16 elements
Subst.Gr:
may substitute for element mule:abstract-global-endpoint
Defined:
globally; see XML source
Used:
never
inbound-endpoint Allows a Mule service to receive requests over HTTPS using a Jetty server.
Type:
inboundEndpointType
Content:
complex, 19 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:
mule:tlsClientKeyStoreType
Content:
empty, 4 attributes
Defined:
locally witnin jettySslConnectorType complexType; see XML source
tls-key-store
Type:
mule:tlsKeyStoreType
Content:
empty, 7 attributes
Defined:
locally witnin jettySslConnectorType complexType; see XML source
tls-protocol-handler
Type:
mule:tlsProtocolHandler
Content:
empty, 1 attribute
Defined:
locally witnin jettySslConnectorType complexType; see XML source
tls-server
Type:
mule:tlsServerTrustStoreType
Content:
empty, 8 attributes
Defined:
locally witnin jettySslConnectorType complexType; see XML source
webapps Allows configuring of a directory which contains WAR files to be served out by Jetty.
Type:
jetty:webappsType
Content:
empty, 5 attributes
Defined:
locally witnin jettySslConnectorType complexType; see XML source
Complex Type Summary
globalEndpointType
Content:
complex, 20 attributes, attr. wildcard, 16 elements
Defined:
globally; see XML source
Used:
at 1 location
inboundEndpointType
Content:
complex, 19 attributes, attr. wildcard, 16 elements
Defined:
globally; see XML source
Used:
at 1 location
jettySslConnectorType
Content:
complex, 2 attributes, attr. wildcard, 6 elements
Defined:
globally; see XML source
Includes:
definitions of 1 attribute, 5 elements
Used:
at 1 location
XML Source
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://www.mulesoft.org/schema/mule/jetty-ssl" xmlns="http://www.mulesoft.org/schema/mule/jetty-ssl" xmlns:http="http://www.mulesoft.org/schema/mule/http" xmlns:jetty="http://www.mulesoft.org/schema/mule/jetty" xmlns:mule="http://www.mulesoft.org/schema/mule/core" 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: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/http" schemaLocation="http://www.mulesoft.org/schema/mule/http/3.3/mule-http.xsd"/>
<xsd:import namespace="http://www.mulesoft.org/schema/mule/jetty" schemaLocation="http://www.mulesoft.org/schema/mule/jetty/3.3/mule-jetty.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 Jetty HTTPS transport provides support for exposing services over HTTPS by embedding a
light-weight Jetty server. You can only define inbound endpoints with this transport.
</xsd:documentation>
<xsd:appinfo>
<schemadoc:short-name>Jetty SSL</schemadoc:short-name>
<schemadoc:page-title>Jetty SSL Transport</schemadoc:page-title>
<schemadoc:artifact-name>jetty</schemadoc:artifact-name>
<schemadoc:transport-features dispatchEvents="false" 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" type="jettySslConnectorType">
<xsd:annotation>
<xsd:documentation>
Allows Mule to expose Mule Services over HTTPS using a Jetty HTTP server. A single Jetty server is created for each connector instance. One connector can serve many endpoints. Users should rarely need to have more than one Jetty connector. The Jetty connector can be configured using a Jetty XML config file, but the default configuration is sufficient for most scenarios.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="jettySslConnectorType">
<xsd:complexContent>
<xsd:extension base="mule:abstractConnectorType">
<xsd:sequence maxOccurs="1" minOccurs="1">
<xsd:element maxOccurs="1" minOccurs="0" name="tls-client" type="mule:tlsClientKeyStoreType"/>
<xsd:element maxOccurs="1" minOccurs="0" name="tls-key-store" type="mule:tlsKeyStoreType"/>
<xsd:element maxOccurs="1" minOccurs="0" name="tls-server" type="mule:tlsServerTrustStoreType"/>
<xsd:element maxOccurs="1" minOccurs="0" name="tls-protocol-handler" type="mule:tlsProtocolHandler"/>
<xsd:element maxOccurs="1" minOccurs="0" name="webapps" type="jetty:webappsType">
<xsd:annotation>
<xsd:documentation>
Allows configuring of a directory which contains WAR files to be served out by Jetty.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="configFile" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The location of the Jetty config file to configure this connector with.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="inbound-endpoint" substitutionGroup="mule:abstract-inbound-endpoint" type="inboundEndpointType">
<xsd:annotation>
<xsd:documentation>
Allows a Mule service to receive requests over HTTPS using a Jetty server.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="inboundEndpointType">
<xsd:complexContent>
<xsd:extension base="http:inboundEndpointType"/>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="endpoint" substitutionGroup="mule:abstract-global-endpoint" type="globalEndpointType">
<xsd:annotation>
<xsd:documentation>
Allows users to configure a global Jetty HTTPS endpoint. Note that this can only be used as an inbound-endpoint reference.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="globalEndpointType">
<xsd:complexContent>
<xsd:extension base="http:globalEndpointType"/>
</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.