cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Pell (JIRA)" <>
Subject [jira] [Commented] (CXF-4597) CXF - jaxws - schema validation for nillable false
Date Fri, 09 Nov 2012 10:00:12 GMT


Jason Pell commented on CXF-4597:

An empty string is still a string, so minOccurs=1 would still be satisfied.  However what
you could do is <xsd:minLength value="1"/>

Obviously you can't do that at the JAXB level, but at Schema level it would certainly force
you to enter at least one character for it to be considered a legal value.

I have created an mailing list post to provide some additional input that you may find of

> CXF - jaxws - schema validation for nillable false
> --------------------------------------------------
>                 Key: CXF-4597
>                 URL:
>             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:

View raw message