2016-08-29 14:00 GMT+04:00 Sergey Beryozkin <sberyoz...@gmail.com>: > > In the vast majority of cases query/header/cookie parameters are simple > properties. Doing the complex mapping from WADL grammar to individual Bean > validation properties only for the sake of enforcing some digital or string > pattern in such (query) properties and then also making sure it works the > other way around (WADL grammar is auto-enhanced based on the avail BeanVal > annotations during WADL generatiopn) is not worth it IMHO, especially that > it will also overloads WADL grammar. > > To be precise, wadl grammar already overloaded in wadl2java Becouse i can write <param style="query" name="name" type="tns:SomeType"/> and see in generated interface param with type of SomeType - enum class generated from xsd
So i think if someone finds work enabling beand validtion annotations worth, i will gladly use this work also. But, again, param validation is not "deal breaker" for wadl2java
