Return-Path: 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 3880FDC58 for ; Mon, 26 Nov 2012 18:21:01 +0000 (UTC) Received: (qmail 31031 invoked by uid 500); 26 Nov 2012 18:21:01 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 31005 invoked by uid 500); 26 Nov 2012 18:21:01 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 30995 invoked by uid 99); 26 Nov 2012 18:21:01 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Nov 2012 18:21:01 +0000 Date: Mon, 26 Nov 2012 18:21:01 +0000 (UTC) From: "Daniel Kulp (JIRA)" To: issues@cxf.apache.org Message-ID: <1778217221.23812.1353954061093.JavaMail.jiratomcat@arcas> In-Reply-To: <932359833.16553.1351009032085.JavaMail.jiratomcat@arcas> Subject: [jira] [Resolved] (CXF-4597) CXF - jaxws - schema validation for nillable false 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-4597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-4597. ------------------------------ Resolution: Not A Problem > CXF - jaxws - schema validation for nillable false > -------------------------------------------------- > > Key: CXF-4597 > URL: https://issues.apache.org/jira/browse/CXF-4597 > Project: CXF > Issue Type: Bug > Components: JAXB Databinding > Affects Versions: 2.6 > Environment: Tomcat web server > Reporter: Balaji Sengeni > Priority: Blocker > Fix For: Invalid > > > Hi , > I apologize, if I have chosen wrong issue type. > I use contract first web service where xsd is defined in external file. > [by default, nillable is false if we haven't mentioned for elements in xsd] > I used jaxws-maven-plugin to import java classes from wsdl. I noticed that nillable attribute is missing for @XmlElement(required = true) [java data type string]. I assume, its the default behaviour, so Jaxb will treat those element as nillable false. > But when the user sends empty tag, my web service accepts that value. > Without touching the xsd (setting minLength for the string), is there a easy way to do non empty string validation? > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira