META-INF.xsd.smooks.db-routing-1.1.xsd Maven / Gradle / Ivy
The newest version!
Smooks SQL Routing Configuration
SQL Executor configuration
The SQL Executor can be used to perform event driven read and write operations on a DataSource,
using data in the bean context as the query/update parameters.
SQL Executor
The SQL statement to be executed. Supports templating in the form of ${variable}.
The variables are resolved from the bean context.
Sets the resultSet specific configuration like the resultSet name, scope and timeToLive.
The element on which the query is executed. With the 'executeBefore'
attribute can be set if the query is executed before or after the element.
The namespace of the executeOnElement element.
The name of the datasource configuration to use. See the datasource configuration
of the Smooks core library.
If the query is executed before the element else it will execute after the element.
Default is 'false'.
ResultSet Row Selector configuration
The ResultSet row Selector can search though a resultset for a specific row.
ResultSet row selector
The MVEL condition to select the correct row.
The error message that is thrown in org.milyn.routing.db.DataSelectionException
exception when no row was found that matches the 'where' query.
If the error message is not set then no exception will be thrown.
The element on which the row selection is executed.
The name of the resultSet to select the row from.
The beanId under which the selected row will be added in the bean context.
If the selection is done before or after the selected element. Default is 'false'.
If the statement is a query statement then the ResultSet will be bound
with this id in the ExecutionContext. Must be specified if the 'statement' is a query
statement, otherwise it is optional.
The scope on which the resultSet will be stored. The scope can be on a EXECUTION or
on a APPLICATION level. On a EXECUTION level the query is executed every time on the selected element.
On a APPLICATION level the query is only executed once for the
whole Smooks instance until the resultSet expires. With the 'timeToLive' attribute the expire time
can be configured. After the resultSet is expired the query will be executed again.
If the 'scope' attribute is set to APPLICATION this attribute determines the expire time
in milliseconds of the resultSet. After the resultSet is expired the query will be executed again.