[java][Microprofile] add config options to disable usage of ApiExceptionMapper

[JacobOJ]

This PR fixes issue #20751 made by @Munken

It is made configurable whether generated Microprofile API clients should RegisterProvider ApiExceptionMapper.
It is also made configurable whether ApiExceptionMapper should be annotated with @Provider, making it a global exception mapper.

Both properties default to true in order to make this a non-breaking change.

PR checklist

• Read the contribution guidelines.
• 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.
• Run the following to build the project and update samples:

  ./mvnw clean package || exit
  ./bin/generate-samples.sh ./bin/configs/*.yaml || exit
  ./bin/utils/export_docs_generators.sh || exit
  

  (For Windows users, please run the script in Git BASH)
  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*.
  IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
• File the PR against the correct branch: master (upcoming 7.x.0 minor release - breaking changes with fallbacks), 8.0.x (breaking changes without fallbacks)
• If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

@bbdouglas @sreeshas @jfiala @lukoyanov @cbornet @jeff9finger @karismann @Zomzog @lwlee2608 @martin-mfg

[JacobOJ]

I see that CircleCI is failing. I'm not sure what the error is or how to fix it

[wing328]

Thanks for the PR but your commit (as shown in the Commits tab) is not linked to your Github account, which means this PR won't count as your contribution in https://github.com/OpenAPITools/openapi-generator/graphs/contributors.

Let me know if you need help fixing it.

Ref: https://github.com/OpenAPITools/openapi-generator/wiki/FAQ#how-can-i-update-commits-that-are-not-linked-to-my-github-account

[wing328]

for the circleci failure, please ignore it for the time being

[wing328]

looks like a rebase went wrong as the PR contains commits from others.

please submit a new one by cherry-picking commits authored by you.

[JacobOJ]

looks like a rebase went wrong as the PR contains commits from others.

please submit a new one by cherry-picking commits authored by you.

On it :)

[JacobOJ]

looks like a rebase went wrong as the PR contains commits from others.

please submit a new one by cherry-picking commits authored by you.

It looks to be fixed now

[JacobOJ]

@wing328 Any update on this?

[wing328]

i think you will need to follow how the rest of microprofile options are set:

        convertPropertyToBooleanAndWriteBack(MICROPROFILE_MUTINY, this::setMicroprofileMutiny);

        convertPropertyToStringAndWriteBack(MICROPROFILE_REST_CLIENT_VERSION, value->microprofileRestClientVersion=value);

as my test shows setting these options to false have no effect in the output

did you test the options locally by setting them to false?

[JacobOJ]

@wing328 Yes, you were right. I changed the code and tested the cli locally.

It works as expected now

[wing328]

👍

i'll run some tests later this week and merge if no more question from me or the community

[martin-mfg]

It seems removing the @Provider annotation makes the generated class useless. If you agree, could you please make it so that microprofileGlobalExceptionMapper controls if this class is generated at all?

[JacobOJ]

Without the @Provider annotation, the mapper does nothing on its own, but you can still register it on RestClients using @RegisterProvider(ApiExceptionMapper.class)

I don't know if that's enough to keep the mapper?

[martin-mfg]

Good point. Let's keep it then.