When publishing a JAX-WS service backed by a Java SEI and setting
, 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:
I'll attach a minimal test case demonstrating the issue.