complexType "restServiceWrapperType"
Namespace:
Content:
complex, 2 attributes, 6 elements
Defined:
globally in mule-http.xsd; see XML source
Includes:
definitions of 2 attributes, 4 elements
Used:
Content Model Diagram
XML Representation Summary
<...
    httpMethod
 = 
("DELETE" | "GET" | "POST") : "GET"
    serviceUrl
 = 
xsd:anySimpleType
    >
   
Content: 
((abstract-interceptor | interceptor-stack)+)?, error-filter?, payloadParameterName*, requiredParameter*, optionalParameter*
</...>
Content Model Elements (6):
All Direct / Indirect Based Elements (1):
Known Usage Locations
Type Definition Detail
Type Derivation Tree
      mule:defaultComponentType (extension)
          restServiceWrapperType
XML Source (w/o annotations (6); see within schema source)
<xsd:complexType name="restServiceWrapperType">
<xsd:complexContent>
<xsd:extension base="mule:defaultComponentType">
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" name="error-filter">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" ref="mule:abstract-filter"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="payloadParameterName" type="mule:valueType"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="requiredParameter" type="mule:keyValueType"/>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="optionalParameter" type="mule:keyValueType"/>
</xsd:sequence>
<xsd:attribute default="GET" name="httpMethod" use="optional">
<xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="DELETE"/>
<xsd:enumeration value="GET"/>
<xsd:enumeration value="POST"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="serviceUrl" use="required"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
Attribute Detail (all declarations; defined in this component only; 2/2)
httpMethod
Type:
anonymous (restriction of xsd:NMTOKEN)
Use:
optional
The HTTP method to use when making the service request.
Attribute Value
enumeration of xsd:NMTOKEN
Enumeration:
"DELETE", "GET", "POST"
Default:
"GET"
Anonymous simpleType
Type Derivation Tree
xsd:NMTOKEN (restriction)
  simpleType
Derivation:
restriction of xsd:NMTOKEN
Facets:
enumeration:
"DELETE", "GET", "POST"
XML Source (w/o annotations (1); see within schema source)
<xsd:attribute default="GET" name="httpMethod" use="optional">
<xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="DELETE"/>
<xsd:enumeration value="GET"/>
<xsd:enumeration value="POST"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>

serviceUrl
Type:
xsd:anySimpleType
Use:
required
The service URL to use when making the request. This should not contain any parameters, since these should be configured on the component. The service URL can contain Mule expressions, so the URL can be dynamic for each message request.
XML Source (w/o annotations (1); see within schema source)
<xsd:attribute name="serviceUrl" use="required"/>
Content Element Detail (all declarations; defined in this component only; 4/6)
error-filter
Type:
anonymous, complex content
An error filter can be used to detect whether the response from the remote service resulted in an error.
XML Source (w/o annotations (1); see within schema source)
<xsd:element maxOccurs="1" minOccurs="0" name="error-filter">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" ref="mule:abstract-filter"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>

optionalParameter
Type:
mule:keyValueType, empty content
These are parameters that if they are on the current message will be added to the request, otherwise they will be ignored. The Key maps to the parameter name, the value can be any one of the valid expressions supported by Mule.
XML Source (w/o annotations (1); see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="optionalParameter" type="mule:keyValueType"/>

payloadParameterName
Type:
mule:valueType, empty content
If the payload of the message is to be attached as a URL parameter, this should be set to the parameter name. If the message payload is an array of objects that multiple parameters can be set to, use each element in the array.
XML Source (w/o annotations (1); see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="payloadParameterName" type="mule:valueType"/>

requiredParameter
Type:
mule:keyValueType, empty content
These are parameters that must be available on the current message for the request to be successful. The Key maps to the parameter name, the value can be any one of the valid expressions supported by Mule.
XML Source (w/o annotations (1); see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="requiredParameter" type="mule:keyValueType"/>

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.