[Java*] BeanValidation for all Java languages

[jfiala]

Description

BeanValidation support has been added in #4003 for Java and jaxrs-cxf/jaxrs-cxf-client.
This needs to be added to all other Java languages

• jaxrs-spec
• jaxrs (Jersey2 + library jersey1)
• jaxrs-resteasy
• jaxrs-cxf-cdi
• spring (default library spring-boot + library spring-mvc, spring-cloud)

Related issues

PR Beanvalidation annotation for Java and CXF #4003
Issues with language jaxrs-spec #4509

Issues with language jaxrs-spec (see #4509)

• the api is generated as class, but IMHO this should be an interface!?
• Jaxrs Response is used instead of the real response data type
• @apiresponse uses wrong response type (the return type, not the response type of the contract)
• src/gen/java is not added to the build path
• "Attachment" is used for attachments, but no import is added for this (I think org.apache.cxf.jaxrs.ext.multipart.Attachment is referenced, but this is CXF-specific)

Update: moved all the issues with jaxrs-spec to #4509

Support for @DecimalMin/@DecimalMax

Also add support for @DecimalMin/@DecimalMax

• jaxrs-spec
• jaxrs (Jersey2 + library jersey1)
• jaxrs-resteasy
• jaxrs-cxf-cdi

Final Cleanup (PR #4635)

• move beanvalidation code to AbstractJavaJAXRSServerCodegen.java
  (so it will stay redundant in AbstractJavaJAXRSServerCodegen.java and SpringCodegen.java) or to AbstractJavaCodegen?
• Backport support for @DecimalMin/@DecimalMax
  backport to languages which already have beanvalidation annotation support:
  • java
  • jaxrs-cxf / jaxrs-cxf-client

Final Cleanup implemented in PR #4635

[jfiala]

@wing328 If you like I can cycle through the language templates and add (optional) beanvalidation support there. Or do you prefer the language maintainers to do the job?

[wing328]

@jfiala if you've time, please add the bean validation support. I'm sure the community and the template owner would appreciate your effort.

[cbornet]

Small remark: if bean validation is an option, it should be activated by default (since you expect the generated code to follow the contract established by the swagger spec)

[deveshpujari]

@jfiala

We would like to get support for server side code generation for jaxrs ( jersey2) with JSR303 annotations. We are doing topdown approach of writing apis in swagger editor and generating the code. I would really appreciate if you prioritize the JSR303 addition to server code for jaxrs ( jersey2). Will it add support for custom annotation also ? Thanks.

[jfiala]

@deveshpujari @wing328 added beanvalidation support to jaxrs-spec, I also had to fix an issue with outer Enums. BeanValidation annotations are now active by default and can be turned off using the CLI parameter useBeanValidation.

Additional issues with jaxrs-spec:

• the api is generated as class, but IMHO this should be an interface!?
• Jaxrs Response is used instead of the real response data type
• @apiresponse uses wrong response type (the return type, not the response type of the contract)
• src/gen/java is not added to the build path
• "Attachment" is used for attachments, but no import is added for this (I think org.apache.cxf.jaxrs.ext.multipart.Attachment is referenced, but this is CXF-specific)

I suggest fixing those in a separate issue for jaxrs-spec.