Pattern:validator cannot have filter and outbound endpoint child elements.

• User impact:

  Medium
• Log Output:

  Hide

  ...
  Root Exception stack trace:
  java.lang.IllegalArgumentException: validationFilter can't be null
  nbsp;nbsp;nbsp;nbsp;at org.apache.commons.lang.Validate.notNull(Validate.java:203)
  nbsp;nbsp;nbsp;nbsp;at org.mule.construct.Validator.<init>(Validator.java:76)
  nbsp;nbsp;nbsp;nbsp;at org.mule.construct.builder.ValidatorBuilder.buildFlowConstruct(ValidatorBuilder.java:69)
  + 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything)
  ...

  Show

  ... Root Exception stack trace: java.lang.IllegalArgumentException: validationFilter can't be null nbsp;nbsp;nbsp;nbsp;at org.apache.commons.lang.Validate.notNull(Validate.java:203) nbsp;nbsp;nbsp;nbsp;at org.mule.construct.Validator.<init>(Validator.java:76) nbsp;nbsp;nbsp;nbsp;at org.mule.construct.builder.ValidatorBuilder.buildFlowConstruct(ValidatorBuilder.java:69) + 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything) ...
• Similar Issues:

  None

See the attached ValidatorTestCase.java and validator-config.xml, which has been extended to expose the bug.
Note that the bug will cause all other tests in the case to fail.

The filter is added to the properties of the generic bean definition created from the pattern:validator element with the property name "messageProcessor".
If there is a outbound endpoint child element, it is added to the properties of the generic bean definition created from the pattern:validator element with the property name "messageProcessor", thus overwriting the message property created by the filter child element.
The end result will be an exception thrown by the org.mule.construct.Validator class, since it will receive null-value for the validation filter.
If the outbound endpoint is specified using an attribute of the pattern:validator element, the above problem will not occur.