Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

From Camel 2.9 onwards the Validation component is provided directly in the camel-core.

Options

Div
classconfluenceTableSmall

Option

Default

Description

resourceResolver

null

Camel

Wiki Markup
{div:class=confluenceTableSmall} || Option || Default || Description || | {{resourceResolver}} | {{null}} | *Camel

2.9:

*

Reference

to

a

{{

org.w3c.dom.ls.LSResourceResolver

}}

in

the

[]. | | {{useDom}} | {{false}} | Whether {{DOMSource}}/{{DOMResult}} or {{SaxSource}}/{{SaxResult}} should be used by the validator. | | {{useSharedSchema}} | {{true}} | *Camel 2.3:* Whether the {{Schema}} instance should be shared or not. This option is introduced to work around a [JDK

.

useDom

false

Whether DOMSource/DOMResult or SaxSource/SaxResult should be used by the validator.

useSharedSchema

true

Camel 2.3: Whether the Schema instance should be shared or not. This option is introduced to work around a JDK 1.6.x

|http://bugs

.

sun.com/bugdatabase/view_bug.do?bug_id=6773084].

Xerces

should

not

have

this

issue.

| | {{failOnNullBody}} | {{true}} | *Camel

failOnNullBody

true

Camel 2.9.5/2.10.3:

*

Whether

to

fail

if

no

body

exists.

| | {{headerName}} | {{null}} | *Camel

headerName

null

Camel 2.11:

*

To

validate

against

a

header

instead

of

the

message

body.

| | {{failOnNullHeader}} | {{true}} | *Camel

failOnNullHeader

true

Camel 2.11:

*

Whether

to

fail

if

no

header

exists

when

validating

against

a

header.

| {div}

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

...