[
https://issues.apache.org/jira/browse/CXF-4597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13493808#comment-13493808
]
Balaji Sengeni commented on CXF-4597:
-------------------------------------
Hi Daniel,
I tried setting the minOccurs="1" as :
<xsd:element name="firstnames" maxOccurs="1">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="100"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
even then ws accepts empty tag as <firstnames/>, is there a way to do minor
changes and have empty string validation? i.e., web service should throw xsd
validation exception if there is any empty tag in the payload (not to accept
empty tag at any level). xml payload should have tag only if it has text value
inside it.
Thanks,
Balaji
> 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
