Schema "mule-cxf.xsd"
Target Namespace:
http://www.mulesoft.org/schema/mule/cxf
Defined Components:
29 global elements, 8 local elements, 19 complexTypes, 1 element group, 4 attribute groups
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
http://www.mulesoft.org/schema/mule/cxf/3.3/mule-cxf.xsd; see XML source
Imports Schemas (5):
core.xsd [src], mule-schemadoc.xsd [src], mule.xsd [src], spring-beans-3.1.xsd [src], xml.xsd [src]
Imported by Schema:
_mule-all-included.xsd
Annotation
Apache CXF is an open source services framework. CXF helps you build and develop services using frontend programming APIs, like JAX-WS. These services can speak a variety of protocols such as SOAP, XML/HTTP, RESTful HTTP, or CORBA and work over a variety of transports such as HTTP, JMS or JBI. The Mule CXF Transport is an evolution of Mule's XFire transport, which provided support for the use of web service integration via Apache CXF. The Mule CXF connector also provides support for WS-Security, WS-Addressing, and WS-Reliable-Messaging.
All Element Summary
abstract-databinding A placeholder for arbitrary extensions as children of the 'mule' element.
Type:
baseDataBinding
Content:
complex, 1 element
Abstract:
(may not be used directly in instance XML documents)
Subst.Gr:
may be substituted with 6 elements
Defined:
globally; see XML source
Used:
at 7 locations
abstract-ws-custom-validator Custom validators to override the default validators used to validate a received security token.
Type:
baseWsCustomValidator
Content:
empty, 2 attributes
Abstract:
(may not be used directly in instance XML documents)
Subst.Gr:
may be substituted with 6 elements
Defined:
globally; see XML source
Used:
at 6 locations
aegis-databinding Configures the Aegis data binding.
Type:
baseDataBinding
Content:
complex, 1 element
Subst.Gr:
may substitute for element abstract-databinding
Defined:
globally; see XML source
Used:
never
bst-token-validator Override BinarySecurityToken validation providing a custom implementation of the Validator instance
Type:
baseWsCustomValidator
Content:
empty, 2 attributes
Subst.Gr:
may substitute for element abstract-ws-custom-validator
Defined:
globally; see XML source
Used:
at 1 location
configuration
Type:
cxfConfigurationType
Content:
complex, 4 attributes, attr. wildcard, 1 element
Subst.Gr:
may substitute for element mule:abstract-extension
Defined:
globally; see XML source
Used:
never
custom-databinding Configures a custom data binding.
Type:
anonymous complexType (extension of baseDataBinding)
Content:
complex, 1 attribute, 1 element
Subst.Gr:
may substitute for element abstract-databinding
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
never
features
Type:
anonymous complexType
Content:
complex, elem. wildcard
Defined:
globally; see XML source
Includes:
definition of elem. wildcard
Used:
at 1 location
inFaultInterceptors Additional incoming fault interceptors.
Type:
interceptors
Content:
complex, elem. wildcard
Defined:
locally witnin commonConfiguration group; see XML source
inInterceptors Additional incoming interceptors for this service.
Type:
interceptors
Content:
complex, elem. wildcard
Defined:
locally witnin commonConfiguration group; see XML source
jaxb-databinding Configures the JAXB data binding.
Type:
baseDataBinding
Content:
complex, 1 element
Subst.Gr:
may substitute for element abstract-databinding
Defined:
globally; see XML source
Used:
never
jaxws-client
Type:
jaxwsClientType
Content:
complex, 10 attributes, attr. wildcard, 9 elements
Subst.Gr:
may substitute for elements: mule:abstract-intercepting-message-processor, mule:abstract-message-processor
Defined:
globally; see XML source
Used:
never
jaxws-service
Type:
jaxWsServiceType
Content:
complex, 11 attributes, attr. wildcard, 10 elements
Subst.Gr:
may substitute for elements: mule:abstract-intercepting-message-processor, mule:abstract-message-processor
Defined:
globally; see XML source
Used:
never
jibx-databinding Configures the Jibx data binding.
Type:
baseDataBinding
Content:
complex, 1 element
Subst.Gr:
may substitute for element abstract-databinding
Defined:
globally; see XML source
Used:
never
mule-security-manager A WSS4J Password validator which verifies username/password combinations against the Mule security manager.
Type:
anonymous complexType (extension of beans:identifiedType)
Content:
empty, 2 attributes
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
at 1 location
outFaultInterceptors Additional outgoing fault interceptors.
Type:
interceptors
Content:
complex, elem. wildcard
Defined:
locally witnin commonConfiguration group; see XML source
outInterceptors Additional outgoing interceptors.
Type:
interceptors
Content:
complex, elem. wildcard
Defined:
locally witnin commonConfiguration group; see XML source
properties
Type:
anonymous complexType
Content:
complex, elem. wildcard
Defined:
globally; see XML source
Includes:
definition of elem. wildcard
Used:
at 1 location
property
Type:
mule:keyValueType
Content:
empty, 3 attributes
Defined:
locally witnin ws-config element; see XML source
proxy-client
Type:
proxyClientType
Content:
complex, 10 attributes, attr. wildcard, 9 elements
Subst.Gr:
may substitute for elements: mule:abstract-intercepting-message-processor, mule:abstract-message-processor
Defined:
globally; see XML source
Used:
never
proxy-service
Type:
proxyServiceType
Content:
complex, 12 attributes, attr. wildcard, 10 elements
Subst.Gr:
may substitute for elements: mule:abstract-intercepting-message-processor, mule:abstract-message-processor
Defined:
globally; see XML source
Used:
never
saml1-token-validator Override SAML1 token validation providing a custom implementation of the Validator instance
Type:
baseWsCustomValidator
Content:
empty, 2 attributes
Subst.Gr:
may substitute for element abstract-ws-custom-validator
Defined:
globally; see XML source
Used:
at 1 location
saml2-token-validator Override SAML2 token validation providing a custom implementation of the Validator instance
Type:
baseWsCustomValidator
Content:
empty, 2 attributes
Subst.Gr:
may substitute for element abstract-ws-custom-validator
Defined:
globally; see XML source
Used:
at 1 location
schemaLocation The location of any additional schema to be included inside the WSDL.
Type:
xsd:string
Content:
simple
Defined:
locally witnin schemasType complexType; see XML source
schemaLocations
Type:
schemasType
Content:
complex, 1 element
Defined:
locally witnin webServiceType complexType; see XML source
signature-token-validator Override trust verification on a signature providing a custom implementation of the Validator instance
Type:
baseWsCustomValidator
Content:
empty, 2 attributes
Subst.Gr:
may substitute for element abstract-ws-custom-validator
Defined:
globally; see XML source
Used:
at 1 location
simple-client
Type:
simpleClientType
Content:
complex, 8 attributes, attr. wildcard, 9 elements
Subst.Gr:
may substitute for elements: mule:abstract-intercepting-message-processor, mule:abstract-message-processor
Defined:
globally; see XML source
Used:
never
simple-service
Type:
simpleServiceType
Content:
complex, 11 attributes, attr. wildcard, 10 elements
Subst.Gr:
may substitute for elements: mule:abstract-intercepting-message-processor, mule:abstract-message-processor
Defined:
globally; see XML source
Used:
never
source-databinding Configures the Source data binding.
Type:
baseDataBinding
Content:
complex, 1 element
Subst.Gr:
may substitute for element abstract-databinding
Defined:
globally; see XML source
Used:
never
stax
Type:
anonymous complexType (extension of beans:identifiedType)
Content:
empty, 3 attributes
Defined:
globally; see XML source
Includes:
definitions of 2 attributes
Used:
never
stax-databinding Configures the Stax data binding.
Type:
baseDataBinding
Content:
complex, 1 element
Subst.Gr:
may substitute for element abstract-databinding
Defined:
globally; see XML source
Used:
never
timestamp-token-validator Override Timestamp validation providing a custom implementation of the Validator instance
Type:
baseWsCustomValidator
Content:
empty, 2 attributes
Subst.Gr:
may substitute for element abstract-ws-custom-validator
Defined:
globally; see XML source
Used:
at 1 location
username-token-validator Override UsernameToken validation providing a custom implementation of the Validator instance
Type:
baseWsCustomValidator
Content:
empty, 2 attributes
Subst.Gr:
may substitute for element abstract-ws-custom-validator
Defined:
globally; see XML source
Used:
at 1 location
wrapper-component The WebServiceWrapperComponent class allows you to send the result of a web service call to another endpoint.
Type:
wrapperComponentType
Content:
complex, 4 attributes, attr. wildcard, 3 elements
Subst.Gr:
may substitute for elements: mule:abstract-component, mule:abstract-message-processor
Defined:
globally; see XML source
Used:
never
ws-config
Type:
anonymous complexType (extension of mule:annotatedType)
Content:
complex, attr. wildcard, 2 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 2 locations
ws-custom-validator
Type:
anonymous complexType (extension of mule:annotatedType)
Content:
complex, attr. wildcard, 7 elements
Defined:
globally; see XML source
Includes:
definitions of 6 elements
Used:
at 1 location
ws-security Configuration to enable WS-Security
Type:
wsSecurityService
Content:
complex, 2 attributes, attr. wildcard, 4 elements
Subst.Gr:
may substitute for element mule:abstract-extension
Defined:
globally; see XML source
Used:
at 1 location
ws-security (type wsSecurityClient)
Type:
wsSecurityClient
Content:
complex, 2 attributes, attr. wildcard, 2 elements
Defined:
locally witnin outboundType complexType; see XML source
Complex Type Summary
baseDataBinding
Content:
complex, 1 element
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 7 locations
baseWsCustomValidator
Content:
empty, 2 attributes
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
at 7 locations
clientType
Content:
complex, 8 attributes, attr. wildcard, 9 elements
Defined:
globally; see XML source
Includes:
definitions of 2 attributes
Used:
at 3 locations
cxfConfigurationType
Content:
complex, 4 attributes, attr. wildcard, 1 element
Defined:
globally; see XML source
Includes:
definitions of 4 attributes
Used:
at 1 location
interceptors
Content:
complex, elem. wildcard
Defined:
globally; see XML source
Includes:
definition of elem. wildcard
Used:
at 4 locations
jaxwsClientType
Content:
complex, 10 attributes, attr. wildcard, 9 elements
Defined:
globally; see XML source
Includes:
definitions of 2 attributes
Used:
at 1 location
jaxWsServiceType
Content:
complex, 11 attributes, attr. wildcard, 10 elements
Defined:
globally; see XML source
Used:
at 1 location
outboundType
Content:
complex, 5 attributes, attr. wildcard, 9 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 1 location
propertiesType
Content:
complex, 1 element
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
never
proxyClientType
Content:
complex, 10 attributes, attr. wildcard, 9 elements
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
at 1 location
proxyServiceType
Content:
complex, 12 attributes, attr. wildcard, 10 elements
Defined:
globally; see XML source
Used:
at 1 location
schemasType
Content:
complex, 1 element
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 1 location
simpleClientType
Content:
complex, 8 attributes, attr. wildcard, 9 elements
Defined:
globally; see XML source
Used:
at 1 location
simpleServiceType
Content:
complex, 11 attributes, attr. wildcard, 10 elements
Defined:
globally; see XML source
Used:
at 1 location
webServiceType
Content:
complex, 11 attributes, attr. wildcard, 10 elements
Defined:
globally; see XML source
Includes:
definitions of 2 elements
Used:
at 3 locations
wrapperComponentType
Content:
complex, 4 attributes, attr. wildcard, 3 elements
Defined:
globally; see XML source
Includes:
definitions of 4 attributes
Used:
at 1 location
wsSecurityBase
Content:
complex, 2 attributes, attr. wildcard, 1 element
Defined:
globally; see XML source
Includes:
definitions of 2 attributes
Used:
at 2 locations
wsSecurityClient
Content:
complex, 2 attributes, attr. wildcard, 2 elements
Defined:
globally; see XML source
Includes:
definition of 1 element
Used:
at 1 location
wsSecurityService
Content:
complex, 2 attributes, attr. wildcard, 4 elements
Defined:
globally; see XML source
Includes:
definitions of 3 elements
Used:
at 1 location
Element Group Summary
commonConfiguration
Content:
7 elements
Defined:
globally; see XML source
Includes:
definitions of 7 elements
Used:
at 2 locations
Attribute Group Summary
clientAttributes
Content:
1 attribute
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
at 1 location
commonAttributes
Content:
5 attributes
Defined:
globally; see XML source
Includes:
definitions of 5 attributes
Used:
at 2 locations
inboundAttributes
Content:
6 attributes
Defined:
globally; see XML source
Includes:
definitions of 6 attributes
Used:
at 1 location
proxyAttributes
Content:
1 attribute
Defined:
globally; see XML source
Includes:
definition of 1 attribute
Used:
at 2 locations
XML Source
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://www.mulesoft.org/schema/mule/cxf" xmlns="http://www.mulesoft.org/schema/mule/cxf" xmlns:beans="http://www.springframework.org/schema/beans" xmlns:cxf="http://cxf.apache.org/core" 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.springframework.org/schema/beans" schemaLocation="http://www.springframework.org/schema/beans/spring-beans-3.1.xsd"/>
<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://cxf.apache.org/core" schemaLocation="http://cxf.apache.org/schemas/core.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>
Apache CXF is an open source services framework. CXF helps you build and develop services using frontend programming APIs, like JAX-WS. These services can speak a variety of protocols such as SOAP, XML/HTTP, RESTful HTTP, or CORBA and work over a variety of transports such as HTTP, JMS or JBI. The Mule CXF Transport is an evolution of Mule's XFire transport, which provided support for the use of web service integration via Apache CXF. The Mule CXF connector also provides support for WS-Security, WS-Addressing, and WS-Reliable-Messaging.
</xsd:documentation>
<xsd:appinfo>
<schemadoc:short-name>CXF</schemadoc:short-name>
<schemadoc:page-title>CXF Transport</schemadoc:page-title>
<schemadoc:transport-features dispatchEvents="true" 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="configuration" substitutionGroup="mule:abstract-extension" type="cxfConfigurationType"/>
<xsd:complexType name="cxfConfigurationType">
<xsd:complexContent>
<xsd:extension base="mule:abstractExtensionType">
<xsd:attribute name="configurationLocation" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The location of a CXF configuration file, if any needs to be supplied.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute default="true" name="enableMuleSoapHeaders" type="mule:substitutableBoolean">
<xsd:annotation>
<xsd:documentation>
Whether or not CXF should write Mule SOAP headers which pass along the correlation and ReplyTo information. This is true by default, but the Mule SOAP headers are only triggered in situations where there is an existing correlation ID and the ReplyTo header is set. (As of 2.2.1)
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute default="true" name="initializeStaticBusInstance" type="mule:substitutableBoolean">
<xsd:annotation>
<xsd:documentation>
Initialize the static CXF Bus with a Bus configured to use Mule for all transports. This will affect any CXF generated clients that you run standalone. Defaults to true.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute default="_cxfConfiguration" name="name" type="xsd:string">
<xsd:annotation>
<xsd:documentation/>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="simple-service" substitutionGroup="mule:abstract-intercepting-message-processor" type="simpleServiceType"/>
<xsd:complexType name="simpleServiceType">
<xsd:complexContent>
<xsd:extension base="webServiceType"/>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="jaxws-service" substitutionGroup="mule:abstract-intercepting-message-processor" type="jaxWsServiceType"/>
<xsd:complexType name="jaxWsServiceType">
<xsd:complexContent>
<xsd:extension base="webServiceType"/>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="proxy-service" substitutionGroup="mule:abstract-intercepting-message-processor" type="proxyServiceType"/>
<xsd:complexType name="proxyServiceType">
<xsd:complexContent>
<xsd:extension base="webServiceType">
<xsd:attributeGroup ref="proxyAttributes"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="webServiceType">
<xsd:complexContent>
<xsd:extension base="mule:abstractInterceptingMessageProcessorType">
<xsd:sequence>
<xsd:element minOccurs="0" name="schemaLocations" type="schemasType"/>
<xsd:element maxOccurs="1" minOccurs="0" ref="ws-security"/>
<xsd:group ref="commonConfiguration"/>
</xsd:sequence>
<xsd:attributeGroup ref="inboundAttributes"/>
<xsd:attributeGroup ref="commonAttributes"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="simple-client" substitutionGroup="mule:abstract-intercepting-message-processor" type="simpleClientType"/>
<xsd:complexType name="simpleClientType">
<xsd:complexContent>
<xsd:extension base="clientType"/>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="jaxws-client" substitutionGroup="mule:abstract-intercepting-message-processor" type="jaxwsClientType"/>
<xsd:complexType name="jaxwsClientType">
<xsd:complexContent>
<xsd:extension base="clientType">
<xsd:attribute name="clientClass" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The name of the client class that CXF generated using CXF's wsdl2java tool. You must use wsdl2java if you do not have both the client and the server in the same JVM. Otherwise, this can be optional if the endpoint address is the same in both cases.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="port" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The WSDL port you want to use to communicate with the service.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="proxy-client" substitutionGroup="mule:abstract-intercepting-message-processor" type="proxyClientType"/>
<xsd:complexType name="proxyClientType">
<xsd:complexContent>
<xsd:extension base="clientType">
<xsd:attributeGroup ref="proxyAttributes"/>
<xsd:attribute name="port" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The WSDL port you want to use to communicate with the service.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="clientType">
<xsd:complexContent>
<xsd:extension base="outboundType">
<xsd:attributeGroup ref="clientAttributes"/>
<xsd:attribute name="serviceClass" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The class CXF should use to construct its service model for the client.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="decoupledEndpoint" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The reply to endpoint for clients which have WS-Addressing enabled.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="outboundType">
<xsd:complexContent>
<xsd:extension base="mule:abstractInterceptingMessageProcessorType">
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" name="ws-security" type="wsSecurityClient"/>
<xsd:group ref="commonConfiguration"/>
</xsd:sequence>
<xsd:attributeGroup ref="commonAttributes"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:attributeGroup name="proxyAttributes">
<xsd:attribute name="payload">
<xsd:annotation>
<xsd:documentation>
Whether the whole SOAP Envelope, or just the body contents should be sent when in proxy mode.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="envelope"/>
<xsd:enumeration value="body"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:attributeGroup>
<xsd:attributeGroup name="commonAttributes">
<xsd:attribute name="soapVersion">
<xsd:annotation>
<xsd:documentation>
The soapVersion that is going to be used for this endpoint. The specified version is translated into the corresponding bindingId value. This attribute is useful when there's need to avoid the creation of the endpoint with the default binding.
In case the bindingId attribute is set this attribute will override it. If not set and not specified otherwise CXF defaults to SOAP 1.1 binding
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="1.1"/>
<xsd:enumeration value="1.2"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="mtomEnabled" type="mule:substitutableBoolean">
<xsd:annotation>
<xsd:documentation>
Whether or not MTOM (attachment support) is enabled for this endpoint.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="wsdlLocation" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The location of the WSDL for your service. If this is a server side endpoint it will served to your users.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute default="true" name="enableMuleSoapHeaders" type="mule:substitutableBoolean">
<xsd:annotation>
<xsd:documentation>
Whether or not this endpoint should write Mule SOAP headers which pass along the correlation and ReplyTo information. This is true by default, but the Mule SOAP headers are only triggered in situations where there is an existing correlation ID and the ReplyTo header is set. (As of 2.2.1)
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="configuration-ref" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The CXF configuration that should be used.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:attributeGroup>
<xsd:attributeGroup name="inboundAttributes">
<xsd:attribute name="bindingId" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The binding that should be used for this endpoint. It defaults to the SOAP binding by default.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="port" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The WSDL port name of your service.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="namespace" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The service namespace. (As of 2.2.1)
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="service" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The WSDL service name of your service.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="serviceClass" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The class CXF should use to construct its service model. This is optional, and by default it will use the implementation class of your component, on inbound cxf endpoint. But it is mandatory for outbound endpoint when using "aegis" frontend.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="validationEnabled" type="mule:substitutableBoolean">
<xsd:annotation>
<xsd:documentation>
Whether or not validation should be enabled on this service.
Validation only occurs on inbound server messages.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:attributeGroup>
<xsd:group name="commonConfiguration">
<xsd:sequence>
<xsd:element minOccurs="0" ref="properties">
<xsd:annotation>
<xsd:documentation>
Additional properties for this service.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="abstract-databinding">
<xsd:annotation>
<xsd:documentation>
The databinding implementation that should be used. By default, this is JAXB for the JAX-WS frontend and Aegis for the simple frontend.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" ref="features">
<xsd:annotation>
<xsd:documentation>
Any CXF features you want to apply to the client/server. See the CXF documentation for more information on features.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="inInterceptors" type="interceptors">
<xsd:annotation>
<xsd:documentation>
Additional incoming interceptors for this service.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="inFaultInterceptors" type="interceptors">
<xsd:annotation>
<xsd:documentation>
Additional incoming fault interceptors.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="outInterceptors" type="interceptors">
<xsd:annotation>
<xsd:documentation>
Additional outgoing interceptors.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="outFaultInterceptors" type="interceptors">
<xsd:annotation>
<xsd:documentation>
Additional outgoing fault interceptors.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:group>
<xsd:attributeGroup name="clientAttributes">
<xsd:attribute name="operation" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The operation you want to invoke on the outbound endpoint.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<!--
<xsd:attribute name="payloadToArguments" default="nullPayloadAsParameter">
<xsd:annotation>
<xsd:documentation>
This indicates how to treat the payload during the building of the parameters for the cxf call.
It has 2 possible values: "nullPayloadAsParameter" and "nullPayloadAsVoid". They only behave differently if
the payload is of type NullPayload. This could change in the future if we add more possible values here.
"nullPayloadAsParameter" is the default and indicates that if the payload is a NullPayload, it will be sent in the service call as a parameter.
"nullPayloadAsVoid" indicates that if the payload is a NullPayload, then the call will be done as if no parameters were supplied.
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:NMTOKEN">
<xsd:enumeration value="nullPayloadAsParameter" />
<xsd:enumeration value="nullPayloadAsVoid" />
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
-->
</xsd:attributeGroup>
<xsd:element abstract="true" name="abstract-databinding" type="baseDataBinding">
<xsd:annotation>
<xsd:documentation>
A placeholder for arbitrary extensions as children of the 'mule' element. Other transports and modules can extend this if they need to add global elements to the configuration (but consider the more specific elements like abstract-connector first).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="baseDataBinding">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="beans:property">
<xsd:annotation>
<xsd:documentation>
Spring property element for custom configuration.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="aegis-databinding" substitutionGroup="abstract-databinding" type="baseDataBinding">
<xsd:annotation>
<xsd:documentation>
Configures the Aegis data binding. See http://cxf.apache.org/docs/aegis-21.html
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="source-databinding" substitutionGroup="abstract-databinding" type="baseDataBinding">
<xsd:annotation>
<xsd:documentation>
Configures the Source data binding. See http://stackoverflow.com/questions/4212608/getting-raw-xml-parameter-in-jax-ws-webservice-method
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="jaxb-databinding" substitutionGroup="abstract-databinding" type="baseDataBinding">
<xsd:annotation>
<xsd:documentation>
Configures the JAXB data binding. See http://cxf.apache.org/docs/jaxb.html
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="jibx-databinding" substitutionGroup="abstract-databinding" type="baseDataBinding">
<xsd:annotation>
<xsd:documentation>
Configures the Jibx data binding.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="stax-databinding" substitutionGroup="abstract-databinding" type="baseDataBinding">
<xsd:annotation>
<xsd:documentation>
Configures the Stax data binding.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="custom-databinding" substitutionGroup="abstract-databinding">
<xsd:annotation>
<xsd:documentation>
Configures a custom data binding.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="baseDataBinding">
<xsd:attribute name="class" type="xsd:NMTOKEN" use="required"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="schemasType">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="schemaLocation" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The location of any additional schema to be included inside the WSDL.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="properties">
<xsd:complexType>
<xsd:sequence>
<xsd:any maxOccurs="unbounded" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="features">
<xsd:complexType>
<xsd:sequence>
<xsd:any maxOccurs="unbounded" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="interceptors">
<xsd:sequence>
<xsd:any maxOccurs="unbounded" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="propertiesType">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="beans:entry"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="wrapper-component" substitutionGroup="mule:abstract-component" type="wrapperComponentType">
<xsd:annotation>
<xsd:documentation>
The WebServiceWrapperComponent class allows you to send the result of a web service call to another endpoint.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="wrapperComponentType">
<xsd:complexContent>
<xsd:extension base="mule:abstractComponentType">
<xsd:attribute name="address" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The URL of the web service.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="addressFromMessage" type="mule:substitutableBoolean">
<xsd:annotation>
<xsd:documentation>
Specifies that the URL of the web service will be obtained from the message itself.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="wsdlPort" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The WSDL port you want to use to communicate to the service.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="operation" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
The operation you want to invoke on the outbound endpoint.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="stax">
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="beans:identifiedType">
<xsd:attribute name="xmlInputFactory" type="xsd:string"/>
<xsd:attribute name="xmlOutputFactory" type="xsd:string"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="mule-security-manager">
<xsd:annotation>
<xsd:documentation>
A WSS4J Password validator which verifies username/password combinations
against the Mule security manager.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="beans:identifiedType">
<xsd:attribute name="securityManager-ref">
<xsd:annotation>
<xsd:documentation>
The security manager instance to use for the password validator. (Optional)
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="wsSecurityService">
<xsd:complexContent>
<xsd:extension base="wsSecurityBase">
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" ref="mule-security-manager">
<xsd:annotation>
<xsd:documentation>
A WSS4J Password validator which verifies username/password combinations against the Mule security manager.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="0" ref="ws-config">
<xsd:annotation>
<xsd:documentation>
A map containing the WSS4J configuration. The entry key and value should map to the text strings in WSS4J's WSHandlerConstants and WSConstants.
The key is the name of the element respecting Mule's naming format, it will be afterwards transformed to CamelCase to map the
corresponding constants, e.g. password-callback-class will map to the constant passwordCallbackClass.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="1" minOccurs="0" ref="ws-custom-validator">
<xsd:annotation>
<xsd:documentation>
A list of validators that allows to override the default validators used to validate a received security token.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="wsSecurityClient">
<xsd:complexContent>
<xsd:extension base="wsSecurityBase">
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" ref="ws-config">
<xsd:annotation>
<xsd:documentation>
A map containing the WSS4J configuration. The entry key and value should map to the text strings in WSS4J's WSHandlerConstants and WSConstants.
The key is the name of the element respecting Mule's naming format, it will be afterwards transformed to CamelCase to map the
corresponding constants, e.g. password-callback-class will map to the constant passwordCallbackClass.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="ws-security" substitutionGroup="mule:abstract-extension" type="wsSecurityService">
<xsd:annotation>
<xsd:documentation>
Configuration to enable WS-Security
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="wsSecurityBase">
<xsd:complexContent>
<xsd:extension base="mule:abstractExtensionType">
<xsd:attribute name="name" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Name of the WS-Security configuration
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="ref" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Reference to a WS-Security configuration
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="ws-config">
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="mule:annotatedType">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="property" type="mule:keyValueType"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="ws-custom-validator">
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="mule:annotatedType">
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" ref="username-token-validator"/>
<xsd:element maxOccurs="1" minOccurs="0" ref="saml1-token-validator"/>
<xsd:element maxOccurs="1" minOccurs="0" ref="saml2-token-validator"/>
<xsd:element maxOccurs="1" minOccurs="0" ref="timestamp-token-validator"/>
<xsd:element maxOccurs="1" minOccurs="0" ref="signature-token-validator"/>
<xsd:element maxOccurs="1" minOccurs="0" ref="bst-token-validator"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element abstract="true" name="abstract-ws-custom-validator" type="baseWsCustomValidator">
<xsd:annotation>
<xsd:documentation>
Custom validators to override the default validators used to validate a received security token.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="baseWsCustomValidator">
<xsd:complexContent>
<xsd:extension base="beans:identifiedType">
<xsd:attribute name="ref" use="required">
<xsd:annotation>
<xsd:documentation>
The custom validator instance to validate the tokens
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="username-token-validator" substitutionGroup="abstract-ws-custom-validator" type="baseWsCustomValidator">
<xsd:annotation>
<xsd:documentation>
Override UsernameToken validation providing a custom implementation of the Validator instance
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="saml1-token-validator" substitutionGroup="abstract-ws-custom-validator" type="baseWsCustomValidator">
<xsd:annotation>
<xsd:documentation>
Override SAML1 token validation providing a custom implementation of the Validator instance
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="saml2-token-validator" substitutionGroup="abstract-ws-custom-validator" type="baseWsCustomValidator">
<xsd:annotation>
<xsd:documentation>
Override SAML2 token validation providing a custom implementation of the Validator instance
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="timestamp-token-validator" substitutionGroup="abstract-ws-custom-validator" type="baseWsCustomValidator">
<xsd:annotation>
<xsd:documentation>
Override Timestamp validation providing a custom implementation of the Validator instance
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="signature-token-validator" substitutionGroup="abstract-ws-custom-validator" type="baseWsCustomValidator">
<xsd:annotation>
<xsd:documentation>
Override trust verification on a signature providing a custom implementation of the Validator instance
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="bst-token-validator" substitutionGroup="abstract-ws-custom-validator" type="baseWsCustomValidator">
<xsd:annotation>
<xsd:documentation>
Override BinarySecurityToken validation providing a custom implementation of the Validator instance
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</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.