Return-Path: 
 <issues-return-21228-apmail-cxf-issues-archive=cxf.apache.org@cxf.apache.org>
X-Original-To: apmail-cxf-issues-archive@www.apache.org
Delivered-To: apmail-cxf-issues-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 071A19FC8
	for <apmail-cxf-issues-archive@www.apache.org>;
 Wed, 23 May 2012 13:40:43 +0000 (UTC)
Received: (qmail 26834 invoked by uid 500); 23 May 2012 13:40:41 -0000
Delivered-To: apmail-cxf-issues-archive@cxf.apache.org
Received: (qmail 26584 invoked by uid 500); 23 May 2012 13:40:41 -0000
Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@cxf.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@cxf.apache.org>
List-Post: <mailto:issues@cxf.apache.org>
List-Id: <issues.cxf.apache.org>
Reply-To: dev@cxf.apache.org
Delivered-To: mailing list issues@cxf.apache.org
Received: (qmail 26560 invoked by uid 99); 23 May 2012 13:40:41 -0000
Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 May 2012 13:40:41 +0000
Received: from isssues-vm.apache.org (localhost [127.0.0.1])
	by issues-vm (Postfix) with ESMTP id 2A18314281C
	for <issues@cxf.apache.org>; Wed, 23 May 2012 13:40:41 +0000 (UTC)
Date: Wed, 23 May 2012 13:40:41 +0000 (UTC)
From: "Daniel Kulp (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <2028915872.11623.1337780441174.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <304092542.7812.1337693740771.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (CXF-4334) Schema validation does not validate
 elements in soap header
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/CXF-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281606#comment-13281606 ] 

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: 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