All Element Summary | ||||||||||||||
abstract-query |
|
|||||||||||||
abstract-sqlStatementStrategyFactory |
|
|||||||||||||
connector |
|
|||||||||||||
derby-data-source |
|
|||||||||||||
endpoint |
|
|||||||||||||
inbound-endpoint | Receives or fetches data from a database.
|
|||||||||||||
mysql-data-source |
|
|||||||||||||
object-store |
|
|||||||||||||
oracle-data-source |
|
|||||||||||||
outbound-endpoint | You can reference any SQL statement or call a stored procedure on outbound endpoints.
|
|||||||||||||
postgresql-data-source |
|
|||||||||||||
query | Assigns a name (key) to a query (value).
|
|||||||||||||
sqlStatementStrategyFactory | Override the default SqlStatementStrategyFactory.
|
|||||||||||||
transaction | Standard Mule transaction configuration.
|
Complex Type Summary | ||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
The JDBC connector is used to configure the shared behavior for JDBC endpoints that reference the connector.
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
Attribute Group Summary | ||||||||||
|
||||||||||
|
<?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.mulesoft.org/schema/mule/core" schemaLocation="http://www.mulesoft.org/schema/mule/core/3.3/mule.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> 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: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:sequence> <xsd:annotation> <xsd:documentation> The factory that determines the execution strategy based on the SQL provided. </xsd:documentation> </xsd:annotation> </xsd:element> <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: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: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: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: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: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: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:complexContent> <xsd:sequence> </xsd:sequence> <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: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:complexContent> <xsd:sequence> </xsd:sequence> <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:complexContent> <xsd:sequence> </xsd:sequence> <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: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:complexContent> </xsd:complexContent> </xsd:complexType> <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:complexContent> </xsd:complexContent> </xsd:complexType> <xsd:annotation> <xsd:documentation>The key of the query to use.</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:complexContent> </xsd:complexContent> </xsd:complexType> <!-- sqlStatementStrategyFactory element --> <xsd:element abstract="true" name="abstract-sqlStatementStrategyFactory" type="abstractSqlStatementStrategyFactoryType"/> <xsd:element name="sqlStatementStrategyFactory" substitutionGroup="abstract-sqlStatementStrategyFactory" type="sqlStatementStrategyFactoryType"> <xsd:annotation> <xsd:documentation> Override the default SqlStatementStrategyFactory. Determines the execution strategy based on the SQL provided. </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:complexContent> </xsd:extension> </xsd:complexContent> </xsd:complexType> </xsd:attributeGroup> <xsd:element name="object-store" substitutionGroup="mule:abstract-object-store" type="jdbcObjectStoreType"/> <xsd:complexContent> <xsd:sequence> </xsd:sequence> <xsd:annotation> <xsd:documentation> The reference to the jdbcConnector </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> The name of the store </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> The key for the insert query in the connector </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> The key for the select query in the connector </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> The key for the delete query in the connector </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:complexContent> <xsd:annotation> <xsd:documentation> Identifies the pool so that the connector can reference it. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> The JDBC URL that is used for connecting the database. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> Maximum time in seconds that this data source will wait while attempting to connect to a database. A value of zero specifies that the timeout is the default system timeout if there is one; otherwise, it specifies that there is no timeout. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> The transaction isolation level to set on the driver when connecting the database. </xsd:documentation> </xsd:annotation> <xsd:simpleType> <xsd:restriction base="xsd:NMTOKEN"> <xsd:enumeration value="UNSPECIFIED"/> <xsd:enumeration value="NONE"/> <xsd:enumeration value="READ_COMMITTED"/> <xsd:enumeration value="READ_UNCOMMITTED"/> <xsd:enumeration value="REPEATABLE_READ"/> <xsd:enumeration value="SERIALIZABLE"/> </xsd:restriction> </xsd:simpleType> </xsd:attribute> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:complexContent> <xsd:annotation> <xsd:documentation> The user that is used for authentication against the database. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> The password that is used for authentication against the database. </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:complexContent> <xsd:annotation> <xsd:documentation> The user that is used for authentication against the database. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> The password that is used for authentication against the database. </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:element name="oracle-data-source" substitutionGroup="mule:abstract-extension" type="oracleDataSourceType"/> <xsd:complexContent> <xsd:annotation> <xsd:documentation> Allows to configure just the host part of the JDBC URL (and leave the rest of the default JDBC URL untouched). </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> Allows to configure just the port part of the JDBC URL (and leave the rest of the default JDBC URL untouched). </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> Allows to configure just the instance part of the JDBC URL (and leave the rest of the default JDBC URL untouched). </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:element name="mysql-data-source" substitutionGroup="mule:abstract-extension" type="mysqlDataSourceType"/> <xsd:complexContent> <xsd:annotation> <xsd:documentation> The name of the database. Must be configured unless a full JDBC URL is configured. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> Allows to configure just the host part of the JDBC URL (and leave the rest of the default JDBC URL untouched). </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> Allows to configure just the port part of the JDBC URL (and leave the rest of the default JDBC URL untouched). </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:element name="postgresql-data-source" substitutionGroup="mule:abstract-extension" type="postgresqlDataSourceType"/> <xsd:complexContent> <xsd:annotation> <xsd:documentation> The name of the database. Must be configured unless a full JDBC URL is configured. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> Allows to configure just the host part of the JDBC URL (and leave the rest of the default JDBC URL untouched). </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> Allows to configure just the port part of the JDBC URL (and leave the rest of the default JDBC URL untouched). </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:element name="derby-data-source" substitutionGroup="mule:abstract-extension" type="derbyDataSourceType"/> <xsd:complexContent> <xsd:annotation> <xsd:documentation> The name of the database. Must be configured unless a full JDBC URL is configured. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> If true, the database will be created upon first access to the database. See <a href="http://db.apache.org/derby/docs/10.6/ref/rrefattrib26867.html">the derby documentation</a> . </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:extension> </xsd:complexContent> </xsd:complexType> </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. |