[
https://issues.apache.org/jira/browse/CXF-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283251#comment-13283251
]
Eirik Bjorsnos commented on CXF-4334:
-------------------------------------
Hi Freeman,
I've built trunk locally and verified that the tests are all green when run on
2.6.1-SNAPSHOT.
The testcase ZIP has been reattached. Please not that the WSDL was based on
some WSDL helloworld tutorial I found on the web. The rest of the code is all
written by me.
So to be 100% IP clean, you could rewrite a hello world WSDL. Should be pretty
basic stuff for someone who's used to working with this :-)
Thanks for your efforts and the quick solution. We're looking forward to 2.6.1
> 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
> Fix For: 2.6.1, 2.5.4, 2.4.8, 2.3.11
>
> 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
