XML Schema "mule-cxf.xsd"
Target Namespace:
http://www.mulesoft.org/schema/mule/cxf
Defined Components:
11 global elements, 7 local elements, 15 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.0/mule-cxf.xsd; see XML source
Imports Schemas (5):
core.xsd [src], mule-schemadoc.xsd [src], mule.xsd [src], spring-beans-3.0.xsd [src], xml.xsd [src]
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.
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://cxf.apache.org/core" schemaLocation="http://cxf.apache.org/schemas/core.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="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:group ref="commonConfiguration"/>
<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:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="outboundType">
<xsd:complexContent>
<xsd:group ref="commonConfiguration"/>
<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="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 service. 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:attributeGroup>
<xsd:group name="commonConfiguration">
<xsd:sequence>
<xsd:element minOccurs="0" name="configuration-ref">
<xsd:annotation>
<xsd:documentation/>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" ref="configuration"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element minOccurs="0" name="databinding" type="databindingType">
<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. This should be specified in the form of a Spring bean.
</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:complexType name="databindingType">
<xsd:sequence>
<xsd:any maxOccurs="1" minOccurs="0" namespace="##any" processContents="lax"/>
</xsd:sequence>
</xsd:complexType>
<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="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="security-manager-callback">
<xsd:annotation>
<xsd:documentation>
A WSS4J Password callback 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 callback. (Optional)
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
</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.