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:
Maven users will need to add the following dependency to their
pom.xml for this component when using Camel 2.8 or older:
From Camel 2.9 onwards the Validation component is provided directly in the camel-core.
|resourceResolverFactory||DefaultValidatorResourceResolverFactory||Camel 2.17: Reference to a |
Camel 2.9: Reference to a
Camel 2.3: Whether the
Camel 2.9.5/2.10.3: Whether to fail if no body exists.
Camel 2.11: To validate against a header instead of the message body.
Camel 2.11: Whether to fail if no header exists when validating against a header.
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).
Advanced: JMX method clearCachedSchema
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.
Endpoint See Also Include Page