[Bug][Java/Spring] OAS3 related bugfixes and enhancements

[cachescrubber]

Further OAS3 related bugfixes and enhancements. A follow up to #11181.

Fixes

• OAS3 incorrect data type when providing a default value [BUG] [JAVA] OAS3 incorrect data type when providing a default value #11367
• Content mediatype is hardcoded in api.mustache [BUG][Java] Content mediatype is hardcoded in api.mustache #11511
• Duplicate @JsonTypeName annotation [BUG][Java] duplicate @JsonTypeName annotation #11492

Supersedes

• [JavaSpring] Fixed hardcoded media type for Swagger 3 annotation in Spring templates #11519, Credits @p-daniil

Other OAS3 related fixes not included here:

• Fix for multible tags in @Operation annotation #11475

PR checklist

• [x ] Read the contribution guidelines.
• [ x] Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
• [ x] Run the following to build the project and update samples:

  ./mvnw clean package 
  ./bin/generate-samples.sh
  ./bin/utils/export_docs_generators.sh
  

  Commit all changed files.
  This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
  These must match the expectations made by your contribution.
  You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
  For Windows users, please run the script in Git BASH.
• [x ] File the PR against the correct branch: master (5.3.0), 6.0.x
• [x ] If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

[cachescrubber]

@welshm, @wing328 FYI

[cachescrubber]

@wing328 The Samples up-to-date check fails, no idea why. Should be all up 2 date.

[wing328]

cc @OpenAPITools/generator-core-team as the change impacts CodegenModel.

[wing328]

LGTM. For the CI failure, it has been fixed in the master.

[wing328]

LGTM. For the CI failure, it has been fixed in the master.

[cachescrubber]

That was quick. Thanks. If you can, have a look at #11475 (LGTM)

[welshm]

I still think we should make the @Schema annotation work. Are enum values properly documented otherwise?

I'm surprised none of the generated samples changed with this.

[cachescrubber]

There are a few:

@NotNull @Parameter(name = "status", description = "Status values that need to be considered for filter", required = true, schema = @Schema(description = "", allowableValues = { "available", "pending", "sold" })) @Valid @RequestParam(value = "status", required = true) List<String> status
This would be a perfect valid PR. We would need to identify when @Schema should be used and what information springdoc could otherwise deduct form the Spring MVC annotations and/or Method Parameters is affected.

We had the same discussion with the @io.swagger.v3.oas.annotations.parameters.RequestBody annotation.

[welshm]

I'm trying to see if I can get the annotation tk be present with the type field set, and see if they resolves the issue.

If it does, then likely we can always set @Schema - but the openApiType is not currently a value available to Java generators so I'm looking at how to appropriately add that.