Return-Path: 
 <issues-return-15608-apmail-cxf-issues-archive=cxf.apache.org@cxf.apache.org>
Delivered-To: apmail-cxf-issues-archive@www.apache.org
Received: (qmail 64270 invoked from network); 16 Jan 2011 03:13:12 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 16 Jan 2011 03:13:12 -0000
Received: (qmail 85471 invoked by uid 500); 16 Jan 2011 03:13:12 -0000
Delivered-To: apmail-cxf-issues-archive@cxf.apache.org
Received: (qmail 85368 invoked by uid 500); 16 Jan 2011 03:13:10 -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 85358 invoked by uid 99); 16 Jan 2011 03:13:09 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 16 Jan 2011 03:13:09 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 16 Jan 2011 03:13:07 +0000
Received: from thor (localhost [127.0.0.1])
	by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id p0G3CjgO013543
	for <issues@cxf.apache.org>; Sun, 16 Jan 2011 03:12:46 GMT
Message-ID: <24754909.390521295147565792.JavaMail.jira@thor>
Date: Sat, 15 Jan 2011 22:12:45 -0500 (EST)
From: "Benjamin Shults (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Subject: [jira] Commented: (CXF-3233) JAXB xsd validation working on
 incoming messages but not outgoing messages
In-Reply-To: <28531819.192521294333725407.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


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

Benjamin Shults commented on CXF-3233:
--------------------------------------

It reports that it is built from WSDL.

> JAXB xsd validation working on incoming messages but not outgoing messages
> --------------------------------------------------------------------------
>
>                 Key: CXF-3233
>                 URL: https://issues.apache.org/jira/browse/CXF-3233
>             Project: CXF
>          Issue Type: Bug
>          Components: Bus
>    Affects Versions: 2.3.1
>         Environment: WebLogic 10.0, WebSphere 6.1
>            Reporter: Benjamin Shults
>            Assignee: Freeman Fang
>             Fix For: NeedMoreInfo
>
>
> Using CXF 2.3.1.
> Generated Java from WSDLs using JAXB.
> Using 
>     <jaxws:properties>
>         <entry key="schema-validation-enabled" value="true" />
>     </jaxws:properties>
> in the client configuration.
> My test creates an object that fails this particular requirement of the WSDL:
>     <xsd:simpleType name="UUID.Content">
>         <xsd:annotation>
>             <xsd:documentation xml:lang="EN">
>                 Universally Unique Identifier
>                 </xsd:documentation>
>         </xsd:annotation>
>         <xsd:restriction base="xsd:token">
>             <xsd:length value="36" />
>             <xsd:pattern
>                 value="[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}" />
>         </xsd:restriction>
>     </xsd:simpleType>
> However, the message is marshalled and makes it all the way through the outgoing interceptor chain.
> The WSDL is one-way: input-only.
> wsdlLocation is specified in an annotation in the Impls.
> Interestingly, incoming messages that fail validation of this same constraint are blocked by the interceptor chain during unmarshalling.
> I'm testing on WebLogic.  I could also test on WebSphere is needed.
> Other XSD validation failures (such as a missing required element) are being caught by the outgoing marshaller.
> The reason that we upgraded to 2.3.1 from 2.2.6 was that we were seeing similar issues on the inbound messages.  In 2.3.1, complete XSD validation occurs for inbound messages but not for outbound ones.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.