cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <>
Subject [jira] [Commented] (CXF-4334) Schema validation does not validate elements in soap header
Date Wed, 23 May 2012 13:40:41 GMT


Daniel Kulp commented on CXF-4334:

No, ReadHeaders likely  should not. Most of the headers it reads should not be validated (or
would be hard to validate) like the ws-rm/ws-addr/ws-security headers and such.   The SoapHeaderInterceptor
likely needs some updating to just validate headers for parts mentioned in the wsdl.   For
headers that don't match a message defined part, it needs to skip.

> Schema validation does not validate elements in soap header
> -----------------------------------------------------------
>                 Key: CXF-4334
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>            Reporter: Eirik Bjorsnos
>            Assignee: Freeman Fang
>         Attachments:
> 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:
> I'll attach a minimal test case demonstrating the issue.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message