<?xml version="1.0" encoding="UTF-8" standalone="no"?> <xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://www.mulesoft.org/schema/mule/jetty" xmlns="http://www.mulesoft.org/schema/mule/jetty" xmlns:http="http://www.mulesoft.org/schema/mule/http" 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.mulesoft.org/schema/mule/core" schemaLocation="http://www.mulesoft.org/schema/mule/core/3.0/mule.xsd"/> <xsd:import namespace="http://www.mulesoft.org/schema/mule/http" schemaLocation="http://www.mulesoft.org/schema/mule/http/3.0/mule-http.xsd"/> <xsd:import namespace="http://www.mulesoft.org/schema/mule/schemadoc" schemaLocation="http://www.mulesoft.org/schema/mule/schemadoc/3.0/mule-schemadoc.xsd"/> <xsd:annotation> <xsd:documentation> The Jetty transport provides support for exposing services over HTTP by embedding a light-weight Jetty server. You can only define inbound endpoints with this transport. </xsd:documentation> <xsd:appinfo> <schemadoc:short-name>Jetty</schemadoc:short-name> <schemadoc:page-title>Jetty Transport</schemadoc:page-title> <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="jettyConnectorType"> <xsd:annotation> <xsd:documentation> Allows Mule to expose Mule Services over HTTP 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:complexContent> <xsd:annotation> <xsd:documentation> The location of the Jetty config file to configure this connector with. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> Whether to use continuations to free up connections in high load situations. </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 HTTP using a Jetty server. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:complexContent> </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 HTTP endpoint. Note that this can only be used as an inbound-endpoint reference. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:complexContent> </xsd:complexContent> </xsd:complexType> </xsd:schema> |
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. |