Namespace "http://www.mulesoft.org/schema/mule/http"
Targeting Schemas (1):
mule-http.xsd
Targeting Components:
12 global elements, 4 local elements, 6 complexTypes, 1 simpleType, 2 attribute groups
Schema Summary
mule-http.xsd The HTTP transport provides support for exposing services over HTTP and making HTTP client requests from Mule services to external services as part of service event flows.
Target Namespace:
Defined Components:
12 global elements, 4 local elements, 6 complexTypes, 1 simpleType, 2 attribute groups
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
http://www.mulesoft.org/schema/mule/http/3.1/mule-http.xsd; see XML source
Imports Schemas (4):
Imported by Schemas (4):
All Element Summary
body-to-parameter-map-transformer This transformer parses the body of a HTTP request into a Map.
Type:
Content:
empty, 5 attributes
Subst.Gr:
Defined:
globally in mule-http.xsd; see XML source
Used:
never
connector Allows Mule to communicate over HTTP.
Type:
Content:
complex, 22 attributes, 5 elements
Subst.Gr:
may substitute for element mule:abstract-connector
Defined:
globally in mule-http.xsd; see XML source
Used:
never
endpoint Configures a 'global' HTTP endpoint that can be referenced by services.
Type:
Content:
complex, 20 attributes, 12 elements
Subst.Gr:
may substitute for element mule:abstract-global-endpoint
Defined:
globally in mule-http.xsd; see XML source
Used:
never
error-filter An error filter can be used to detect whether the response from the remote service resulted in an error.
Type:
anonymous complexType
Content:
complex, 1 element
Defined:
Includes:
definition of 1 element
http-response-to-object-transformer A transformer that converts an HTTP response to a Mule Message.
Type:
Content:
empty, 5 attributes
Subst.Gr:
Defined:
globally in mule-http.xsd; see XML source
Used:
never
http-response-to-string-transformer Converts an HTTP response payload into a string.
Type:
Content:
empty, 5 attributes
Subst.Gr:
Defined:
globally in mule-http.xsd; see XML source
Used:
never
inbound-endpoint An inbound HTTP endpoint exposes a service over HTTP, essentially making it an HTTP server.
Type:
Content:
complex, 19 attributes, 12 elements
Subst.Gr:
may substitute for element mule:abstract-inbound-endpoint
Defined:
globally in mule-http.xsd; see XML source
Used:
never
message-to-http-response-transformer This transformer will create a valid HTTP response using the current message and any HTTP headers set on the current message.
Type:
Content:
empty, 5 attributes
Subst.Gr:
Defined:
globally in mule-http.xsd; see XML source
Used:
never
object-to-http-request-transformer This transformer will create a valid HTTP request using the current message and any HTTP headers set on the current message.
Type:
Content:
empty, 5 attributes
Subst.Gr:
Defined:
globally in mule-http.xsd; see XML source
Used:
never
optionalParameter These are parameters that if they are on the current message will be added to the request, otherwise they will be ignored.
Type:
Content:
empty, 3 attributes
Defined:
outbound-endpoint The HTTP outbound endpoint allows Mule to send requests to external servers or Mule inbound HTTP endpoints using the HTTP protocol.
Type:
Content:
complex, 20 attributes, 12 elements
Subst.Gr:
may substitute for element mule:abstract-outbound-endpoint
Defined:
globally in mule-http.xsd; see XML source
Used:
never
payloadParameterName If the payload of the message is to be attached as a URL parameter, this should be set to the parameter name.
Type:
Content:
empty, 2 attributes
Defined:
polling-connector Allows Mule to poll an external HTTP server and generate events from the result.
Type:
Content:
complex, 25 attributes, 5 elements
Subst.Gr:
may substitute for element mule:abstract-connector
Defined:
globally in mule-http.xsd; see XML source
Used:
never
request-wildcard-filter (As of 2.2.2) The request-wildcard-filter element can be used to restrict the request by applying wildcard expressions to the URL.
Type:
Content:
empty, 3 attributes
Subst.Gr:
Defined:
globally in mule-http.xsd; see XML source
Used:
never
requiredParameter These are parameters that must be available on the current message for the request to be successful.
Type:
Content:
empty, 3 attributes
Defined:
rest-service-component Built-in RestServiceWrapper can be used to proxy REST style services as local Mule components.
Type:
Content:
complex, 2 attributes, 6 elements
Subst.Gr:
Defined:
globally in mule-http.xsd; see XML source
Used:
never
Complex Type Summary
globalEndpointType
Content:
complex, 20 attributes, 12 elements
Defined:
globally in mule-http.xsd; see XML source
Includes:
definition of 1 attribute
Used:
httpConnectorType
Content:
complex, 22 attributes, 5 elements
Defined:
globally in mule-http.xsd; see XML source
Includes:
definitions of 6 attributes
Used:
httpPollingConnectorType
Content:
complex, 25 attributes, 5 elements
Defined:
globally in mule-http.xsd; see XML source
Includes:
definitions of 3 attributes
Used:
inboundEndpointType
Content:
complex, 19 attributes, 12 elements
Defined:
globally in mule-http.xsd; see XML source
Used:
outboundEndpointType
Content:
complex, 20 attributes, 12 elements
Defined:
globally in mule-http.xsd; see XML source
Includes:
definition of 1 attribute
Used:
restServiceWrapperType
Content:
complex, 2 attributes, 6 elements
Defined:
globally in mule-http.xsd; see XML source
Includes:
definitions of 2 attributes, 4 elements
Used:
Simple Type Summary
httpMethodTypes
Defined:
globally in mule-http.xsd; see XML source
Used:
Attribute Group Summary
addressAttributes
Content:
Defined:
globally in mule-http.xsd; see XML source
Includes:
definitions of 5 attributes
Used:
propertyAttributes
Content:
Defined:
globally in mule-http.xsd; see XML source
Includes:
definitions of 3 attributes
Used:

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.