[REQ] Disable TYPE_USE @Valid bean validation annotation

[jpraet]

Is your feature request related to a problem? Please describe.

As of openapi-generator 7.2.0 the following code gets generated with the jaxrs-spec generator:

private @Valid List<@Valid Address> addresses;

In openapi-generator 7.1.0 this was:

private @Valid List<Address> addresses;

The @Valid annotation does not permit location TYPE_USE on Java EE 7 (bean-validation 1.1).
This is only possible since Java EE 8 (bean-validation 2.0).

Describe the solution you'd like

Option to disable TYPE_USE @Valid annotation, or to configure the bean-validation version to use.

[martin-mfg]

The @Valid annotation does not permit location TYPE_USE on Java EE 7 (bean-validation 1.1).
This is only possible since Java EE 8 (bean-validation 2.0).

Hi @jpraet, code generated by the jaxrs-spec generator does use Java 8, according to e.g.

openapi-generator/samples/server/petstore/jaxrs-spec/pom.xml

Line 133 in d29196a

<java.version>1.8</java.version>

. So there shouldn't be a problem, right?

[jpraet]

It's not really related to the JDK version, but rather to the Java EE / Bean Validation version.

Java EE 7 / Bean Validation 1.1: https://docs.jboss.org/hibernate/beanvalidation/spec/1.1/api/javax/validation/Valid.html
Java EE 8 / Bean Validation 2.0: https://docs.jboss.org/hibernate/beanvalidation/spec/2.0/api/javax/validation/Valid.html

Anyway the generated server code indeed also specifies:

openapi-generator/samples/server/petstore/jaxrs-spec/pom.xml

Line 141 in d29196a

<beanvalidation-version>2.0.2</beanvalidation-version>

But I think many people, myself included, use the openapi-generator only for generating the model and api interfaces, and not for generating an entire project with maven pom.xml included. Besides, the bean validation dependency is provided-scoped, as it is indeed provided by the target application server.

And unfortunately I still have to deal with some applications running on WebSphere 8.5 = Java EE 7.
As a workaround, I have configured <useBeanValidation>false</useBeanValidation> for those applications.

The bean validation annotations are also causing trouble in JBoss EAP 7.4 applications. There, it is not exactly caused by the TYPE_USE annotations themselves (as JBoss EAP 7.4 supports Java EE 8), but because these annotations are also placed on the final / private builder classes (<generateBuilders>true</generateBuilders>) causing CDI problems.

I have a PR #19580 open for that one.