This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • Validation
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Validation Component

The Validation component performs XML validation of the message body using the JAXP Validation API using any of the supported XML schema languages, which defaults to XML Schema

Note that the Jing component also supports the following schema languages which are useful

The MSV component also supports RelaxNG XML Syntax.

URI format


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


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).

Error rendering macro 'code': Invalid value specified for parameter 'java.lang.NullPointerException'
    <from uri="direct:start"/>
        <to uri="validator:org/apache/camel/component/validator/schema.xsd"/>
        <to uri="mock:valid"/>
            <to uri="mock:invalid"/>
            <to uri="mock:finally"/>
  • No labels