Since we're on a major migration process of this website, some component documents here are out of sync right now. In the meantime you may want to look at the early version of the new website
https://camel.apache.org/staging/
We would very much like to receive any feedback on the new site, please join the discussion on the Camel user mailing list.
Validation ComponentThe 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. URI formatWhere 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:
Maven users will need to add the following dependency to their From Camel 2.9 onwards the Validation component is provided directly in the camel-core. Options
ExampleThe 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). Advanced: JMX method clearCachedSchemaSince Camel 2.17, you can force that the cached schema in the validator endpoint is cleared and reread with the next process call with the JMX operation Advanced: Global Option "CamelXmlValidatorAccessExternalDTD"Since Camel 2.19, 2.18.3, and 2.17.6 the default schema factory no longer allows reading external DTDs and external DTD entities. To achieve the old behavior where it was possible to access external DTDs and DTDs entities you can set the CamelContext global option "CamelXmlValidatorAccessExternalDTD" to "true". Prior to 2.19 global options where called properties. |