Not able to make @webparam mandatory field JAX-WS

Question

I am trying to make my @webparam mandatory using (@XmlElement(required=true) but the generated XSD still shows this as minOccurs="0". Also tried setting nillable=false but still not working.

Here is my web method :

@WebMethod
@WebResult(name = "Biller")
public Biller getBiller(@XmlElement(required=true) @WebParam(name = "billerId") Integer billerId){}

Please suggest.

See https://stackoverflow.com/questions/7869494/xmlelementrequired-true-for-webparam-does-not-work — Ori Marko, Apr 04 '18 at 06:37
its 2.6.1. Also added @EndpointProperties(value = { @EndpointProperty(key = "schema-validation-enabled", value = "true") }) in my Web service class — Mrinal Sharma, Apr 04 '18 at 07:12
Tried adding @SchemaValidation(enabled=true), still no scuccess. — Mrinal Sharma, Apr 04 '18 at 12:28
and does your xsd become correct if you change `Integer biller` to `int biller` ( primitive int ) ? — Sabir Khan, Apr 04 '18 at 16:02
@SabirKhan when I changed parameter to primitive int , the xsd is like Also in the request XML in SOAPUI I can see optional comment as removed. but if i remove the element API call still works fine. and what if my webparam is of String or any other Wrapper type. — Mrinal Sharma, Apr 04 '18 at 16:22

score 1 · Accepted Answer · answered Apr 05 '18 at 04:01

As specified by me in comments - either you need to wrap your Integer variable into some Java POJO and apply rules for specific fields in that POJO or change to primitive type because - reference types are always optional but constituent fields of wrapper types can be made required or optional. Primitive types are always required.

Refer this answer

Then comes the question about default values - and for that refer Answers to this question and summary is - if nothing is specified -

minOccurs and maxOccurs default to 1

Now why your call succeeds with SOAP UI - Your xsd is correct and that is acknowledged by SOAP UI so my guess is client might be attaching some default values when its missing. I haven't used SOAP UI. Try examining your request ans see if value is really missing. If value is indeed missing in request then try to examine as why validation is not kicking in.

Thanks for the anwer, SOAP UI started validating my request against XSD schema when I added @com.sun.xml.ws.developer.SchemaValidation to my Web service class . But now I am getting com.sun.xml.ws.encoding.soap.DeserializationException for response which I am trying to figure out. Thanks agian :) — Mrinal Sharma, Apr 05 '18 at 05:06

Not able to make @webparam mandatory field JAX-WS

1 Answers1