[CXF-4334] Schema validation does not validate elements in soap header

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.3.11, 2.4.8, 2.5.4, 2.6.1
• Estimated Complexity: Unknown
• Assignee: Freeman Yue Fang
• Reporter: Eirik Bjorsnos
• Created: 22/May/12 13:34
• Updated: 05/Jun/12 13:31
• Resolved: 25/May/12 03:30

Description

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.