Sergey,
OK, so there is no option to get query parameter validation for
wadl2java generated java sources in the near future?
So if query parameter validation is desired, one has to switch to
Swagger as contract and generate the BeanValidation-annotations using
Swagger-Codegen or use code first, right?
Best regards,
Johannes
Am 25.08.2016 um 15:16 schrieb Vjacheslav V. Borisov:
2016-08-25 16:58 GMT+04:00 Sergey Beryozkin <sberyoz...@gmail.com>:
https://www.w3.org/Submission/wadl/#x3-90002.4
states the WADL grammar "acts as a container for definitions of the format
of data exchanged during execution..." - this implies the
'wadl:representation'.
These other parameters should really refer to some existing primitive
types defined in XML schema.
I don't think it is realistic or worth the effort to go the route of
introspecting schema types in case the non-representation parameters decide
to refer to some of WADL grammar elements and then adding all these various
BeanVal annotations because as I said IMHO it will overload what WADL
grammar is for.
If WADL submission ever gets further and we see the future versions saying
yes the non-representation parameters can refer to WADL grammar then we can
revisit this enhancement request.
Adding only @Valid seems realistic though
Yes, this is "quick win" to allow JSR303 validation work with wadl2java
