You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2012/05/23 14:59:41 UTC
[jira] [Assigned] (CXF-4334) Schema validation does not validate
elements in soap header
[ https://issues.apache.org/jira/browse/CXF-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang reassigned CXF-4334:
---------------------------------
Assignee: Freeman Fang
> Schema validation does not validate elements in soap header
> -----------------------------------------------------------
>
> Key: CXF-4334
> URL: https://issues.apache.org/jira/browse/CXF-4334
> Project: CXF
> Issue Type: Bug
> Reporter: Eirik Bjorsnos
> Assignee: Freeman Fang
> Attachments: CXF-4334-header-validation-testcase.zip
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira