Schema validation does not validate elements in soap header

When publishing a JAX-WS service backed by a Java SEI and setting

properties.put(Message.SCHEMA_VALIDATION_ENABLED, Boolean.TRUE.toString());

, then missing / wrong soap header content in the request is detected with a soap:Fault.

However, when the JAX-WS service is backed by a Provider<Source> annotated with @WebServiceProvider, then invalid soap body content is detected, but invalid header content is not.

I would expect that when SCHEMA_VALIDATION_ENABLED is set to true, then invalid content should cause soap:Fault for header and body content, regardless of the service being backed by a Java SEI or a Provider<Source>.

I think this mail thread discusses the same issue:

http://cxf.547215.n5.nabble.com/Schema-validation-is-not-validating-elements-from-SoapHeader-td4705565.html

I'll attach a minimal test case demonstrating the issue.