XQuery
Query and/or transform XML payloads using XQuery and Saxon.
What’s inside
-
XQuery component, URI syntax:
xquery:resourceUri
Please refer to the above links for usage and configuration details.
Maven coordinates
<dependency>
<groupId>org.apache.camel.springboot</groupId>
<artifactId>camel-saxon-starter</artifactId>
</dependency> Spring Boot Auto-Configuration
The starter supports 12 options, which are listed below.
| Name | Description | Default | Type |
|---|---|---|---|
camel.component.xquery.autowired-enabled | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | Boolean |
camel.component.xquery.bridge-error-handler | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions (if possible) occurred while the Camel consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. Important: This is only possible if the 3rd party component allows Camel to be alerted if an exception was thrown. Some components handle this internally only, and therefore bridgeErrorHandler is not possible. In other situations we may improve the Camel component to hook into the 3rd party component and make this possible for future releases. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | Boolean |
camel.component.xquery.configuration | To use a custom Saxon configuration. The option is a net.sf.saxon.Configuration type. | Configuration | |
camel.component.xquery.configuration-properties | To set custom Saxon configuration properties | Object> | |
camel.component.xquery.enabled | Whether to enable auto configuration of the xquery component. This is enabled by default. | Boolean | |
camel.component.xquery.lazy-start-producer | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | Boolean |
camel.component.xquery.module-u-r-i-resolver | To use the custom ModuleURIResolver. The option is a net.sf.saxon.lib.ModuleURIResolver type. | ModuleURIResolver | |
camel.language.xquery.configuration-ref | Reference to a saxon configuration instance in the registry to use for xquery (requires camel-saxon). | String | |
camel.language.xquery.enabled | Whether to enable auto configuration of the xquery language. This is enabled by default. | Boolean | |
camel.language.xquery.namespace | Injects the XML Namespaces of prefix to uri mappings. | PropertyDefinition> | |
camel.language.xquery.source | Source to use, instead of message body. You can prefix with variable:, header:, or property: to specify kind of source. Otherwise, the source is assumed to be a variable. Use empty or null to use default source, which is the message body. | String | |
camel.language.xquery.trim | Whether to trim the source code to remove leading and trailing whitespaces and line breaks. | true | Boolean |