The Validation component performs XML validation of the message body using the JAXP Validation API and based on any of the supported XML schema languages, which defaults to XML Schema
Note that the Jing component also supports the following useful schema languages:
The MSV component also supports RelaxNG XML Syntax.
validator:someLocalOrRemoteResource
Where someLocalOrRemoteResource is some URL to a local resource on the classpath or a full URL to a remote resource or resource on the file system which contains the XSD to validate against. For example:
msv:org/foo/bar.xsd
msv:file:../foo/bar.xsd
validator:com/mypackage/myschema.xsd
Option | Default | Description |
---|---|---|
resourceResolver
|
null
|
Apache Camel 2.9: Specifies
a reference to an
org.w3c.dom.ls.LSResourceResolver in
the Camel Registry. |
useDom
|
false
|
Apache Camel 2.0: Whether
DOMSource /{{DOMResult}} or
SaxSource /{{SaxResult}} should be
used by the validator. |
useSharedSchema
|
true
|
Apache Camel 2.3: Whether
the Schema instance should be shared or
not. This option is introduced to work around a JDK 1.6.x bug. Xerces should not have this
issue. |
failIfNoBody
|
true
|
Apache Camel 2.9.5, 2.10.3: Specifies whether to fail when no body exists. |
The following example shows how to configure a route from endpoint direct:start which then goes to one of two endpoints, either mock:valid or mock:invalid based on whether or not the XML matches the given schema (which is supplied on the classpath).
<camelContext xmlns="http://camel.apache.org/schema/spring"> <route> <from uri="direct:start"/> <doTry> <to uri="validator:org/apache/camel/component/validator/schema.xsd"/> <to uri="mock:valid"/> <doCatch> <exception>org.apache.camel.ValidationException</exception> <to uri="mock:invalid"/> </doCatch> <doFinally> <to uri="mock:finally"/> </doFinally> </doTry> </route> </camelContext>