XML Schema "mule-jdbc.xsd"
Target Namespace:
http://www.mulesoft.org/schema/mule/jdbc
Defined Components:
9 global elements, 9 complexTypes, 2 attribute groups
Default Namespace-Qualified Form:
Local Elements: qualified; Local Attributes: unqualified
Schema Location:
http://www.mulesoft.org/schema/mule/jdbc/3.1/mule-jdbc.xsd; see XML source
Imports Schemas (3):
mule-schemadoc.xsd [src], mule.xsd [src], xml.xsd [src]
Annotation
The JDBC transport allows data to be retrieved from and written to any database that supports a JDBC driver. It also supports invoking stored precedures.
XML Source
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://www.mulesoft.org/schema/mule/jdbc" xmlns="http://www.mulesoft.org/schema/mule/jdbc" 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 JDBC transport allows data to be retrieved from and written to any database that supports a JDBC driver. It also supports invoking stored precedures.
</xsd:documentation>
<xsd:appinfo>
<schemadoc:short-name>JDBC</schemadoc:short-name>
<schemadoc:page-title>JDBC Transport</schemadoc:page-title>
<schemadoc:transport-features dispatchEvents="true" receiveEvents="true" requestEvents="true" retries="true" streaming="false" transactionTypes="local, XA" transactions="true">
<schemadoc:MEPs default="one-way" supported="one-way, request-response"/>
</schemadoc:transport-features>
</xsd:appinfo>
</xsd:annotation>
<xsd:element name="connector" substitutionGroup="mule:abstract-connector" type="jdbcConnectorType"/>
<xsd:complexType name="jdbcConnectorType">
<xsd:annotation>
<xsd:documentation>
The JDBC connector is used to configure the shared behavior for JDBC endpoints that reference the connector. DataSources, Queries, and Polling Intervals are some of the key properties configured on the JDBC connector.
</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="mule:connectorType">
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" ref="abstract-sqlStatementStrategyFactory">
<xsd:annotation>
<xsd:documentation>
The factory that determines the
execution strategy based on the SQL provided.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="abstract-query">
<xsd:annotation>
<xsd:documentation>
Defines a set of queries. Each query has a key
and a value (SQL statement). Queries are later referenced by
key.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="pollingFrequency" type="mule:substitutableLong">
<xsd:annotation>
<xsd:documentation>
The delay in milliseconds that will be used during two subsequent polls to the database. This is only applied to queries configured on inbound endpoints.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="dataSource-ref" type="xsd:string" use="required">
<xsd:annotation>
<xsd:documentation>
Reference to the JDBC DataSource object. This object is typically created using Spring. When using XA transactions, an XADataSource object must be provided.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="queryRunner-ref" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Reference to the QueryRunner object, which is the object that actually runs the Query. This object is typically created using Spring. Default is org.apache.commons.dbutils.QueryRunner.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="resultSetHandler-ref" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Reference to the ResultSetHandler object, which is the object that determines which java.sql.ResultSet gets handled. This object is typically created using Spring. Default is org.apache.commons.dbutils.handlers.MapListHandler, which steps through the ResultSet and stores records as Map objects on a List.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="transactionPerMessage" type="mule:substitutableBoolean">
<xsd:annotation>
<xsd:documentation>
Whether each database record should be received in a separate transaction. If false, there will be a single transaction for the entire result set. Default is true.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute default="-1" name="queryTimeout" type="xsd:int">
<xsd:annotation>
<xsd:documentation>
The timeout in seconds that will be used as a query timeout for the SQL statement
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="inbound-endpoint" substitutionGroup="mule:abstract-inbound-endpoint" type="inboundEndpointType">
<xsd:annotation>
<xsd:documentation>
Receives or fetches data from a database. You can reference SQL select statements or call stored procedures on inbound endpoints. Statements on the inbound endpoint get invoked periodically according to the pollingInterval. Statements that contain an insert, update, or delete are not allowed.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="inboundEndpointType">
<xsd:complexContent>
<xsd:extension base="mule:inboundEndpointWithXaType">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="abstract-query"/>
</xsd:sequence>
<xsd:attributeGroup ref="addressAttributes"/>
<xsd:attribute default="-1" name="queryTimeout" type="xsd:int">
<xsd:annotation>
<xsd:documentation>
The timeout in seconds that will be used as a query timeout for the SQL statement
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="outbound-endpoint" substitutionGroup="mule:abstract-outbound-endpoint" type="outboundEndpointType">
<xsd:annotation>
<xsd:documentation>
You can reference any SQL statement or call a stored procedure on outbound endpoints. Statements on the outbound endpoint get invoked synchronously. SQL select statements or stored procedures may return output that is handled by the ResultSetHandler and then attached to the message as the payload.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="outboundEndpointType">
<xsd:complexContent>
<xsd:extension base="mule:outboundEndpointWithXaType">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="abstract-query"/>
</xsd:sequence>
<xsd:attributeGroup ref="addressAttributes"/>
<xsd:attribute default="-1" name="queryTimeout" type="xsd:int">
<xsd:annotation>
<xsd:documentation>
The timeout in seconds that will be used as a query timeout for the SQL statement
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="endpoint" substitutionGroup="mule:abstract-global-endpoint" type="globalEndpointType"/>
<xsd:complexType name="globalEndpointType">
<xsd:complexContent>
<xsd:extension base="mule:globalEndpointWithXaType">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" ref="abstract-query"/>
</xsd:sequence>
<xsd:attributeGroup ref="addressAttributes"/>
<xsd:attribute default="-1" name="queryTimeout" type="xsd:int">
<xsd:annotation>
<xsd:documentation>
The timeout in seconds that will be used as a query timeout for the SQL statement
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!-- Define a type hierarchy so that the EE transport can re-define the "query" element. -->
<xsd:element abstract="true" name="abstract-query" type="abstractQueryType"/>
<xsd:complexType name="abstractQueryType">
<xsd:complexContent>
<xsd:extension base="mule:keyValueType"/>
</xsd:complexContent>
</xsd:complexType>
<xsd:element name="query" substitutionGroup="abstract-query" type="queryType">
<xsd:annotation>
<xsd:documentation>
Assigns a name (key) to a query (value). Queries
are then referenced by key, such as jdbc://myQuery for
<![CDATA[
<jdbc:query key="myQuery" value="select * from table"/>
]]>
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="queryType">
<xsd:complexContent>
<xsd:extension base="abstractQueryType"/>
</xsd:complexContent>
</xsd:complexType>
<xsd:attributeGroup name="addressAttributes">
<xsd:attribute name="queryKey" type="xsd:string">
<xsd:annotation>
<xsd:documentation>The key of the query to use.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attribute name="pollingFrequency" type="mule:substitutableLong">
<xsd:annotation>
<xsd:documentation>
The delay in milliseconds that will be used during two subsequent polls to the database.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:attributeGroup>
<xsd:element name="transaction" substitutionGroup="mule:abstract-transaction" type="transactionType">
<xsd:annotation>
<xsd:documentation>
Standard Mule transaction configuration. See [Transaction Management] for usage details.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="transactionType">
<xsd:complexContent>
<xsd:extension base="mule:baseTransactionType"/>
</xsd:complexContent>
</xsd:complexType>
<!--
sqlStatementStrategyFactory element
-->
<xsd:complexType name="abstractSqlStatementStrategyFactoryType"/>
<xsd:annotation>
<xsd:documentation>
Override the default SqlStatementStrategyFactory. Determines the
execution strategy based on the SQL provided.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:complexType name="sqlStatementStrategyFactoryType">
<xsd:complexContent>
<xsd:attributeGroup ref="sqlStatementStrategyFactoryAttributes"/>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:attributeGroup name="sqlStatementStrategyFactoryAttributes">
<xsd:attribute name="class" type="mule:substitutableClass" use="optional"/>
<xsd:attribute name="ref" type="xsd:string" use="optional"/>
</xsd:attributeGroup>
</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.