XML Schema "mule-jetty.xsd"
Target Namespace:
http://www.mulesoft.org/schema/mule/jetty
Defined Components:
3 global elements, 1 local element, 4 complexTypes
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
http://www.mulesoft.org/schema/mule/jetty/3.1/mule-jetty.xsd; see XML source
Imports Schemas (4):
mule-http.xsd [src], mule-schemadoc.xsd [src], mule.xsd [src], xml.xsd [src]
Imported by Schema:
mule-ajax.xsd [src]
Annotation
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.
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" 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.w3.org/XML/1998/namespace"/>
<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:complexType name="jettyConnectorType">
<xsd:complexContent>
<xsd:extension base="mule:abstractConnectorType">
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" name="webapps" type="webappsType">
<xsd:annotation>
<xsd:documentation>
Allows configuring of an 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:attribute name="useContinuations" type="mule:substitutableBoolean">
<xsd:annotation>
<xsd:documentation>
Whether to use continuations to free up connections in high load situations.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="resourceBase" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>
Specifies a local path where files will be served from. The local path gets mapped directly to the path on the 'serverUrl'.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="webappsType">
<xsd:attribute name="port" type="xsd:integer">
<xsd:annotation>
<xsd:documentation>
The port of the Jetty instance.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="host" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The host of the Jetty instance.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="directory" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The directory where webapps can be found.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="serverClasses" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
A comma delimited list of classes which cannot be seen by webapp context classloaders but can be overridden by the webapp.
Defaults to: org.mortbay.jetty.plus.jaas., org.mortbay.jetty., org.slf4j.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="systemClasses" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
A comma delimited list of classes which cannot be overridden by webapp classloaders.
Defaults to: java., javax.servlet., javax.xml., org.mortbay., org.xml.,org.w3c., org.apache.commons.logging., org.apache.log4j.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</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: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 HTTP 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 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.