Created by: UnleashSpirit
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: 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./mvnw clean package ./bin/generate-samples.sh ./bin/utils/export_docs_generators.sh./bin/generate-samples.sh bin/configs/java*. For Windows users, please run the script in Git BASH. -
File the PR against the correct branch: master,5.1.x,6.0.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.
We recently swith from resttemplate to webclient.
We have self signed certificate so we need to allow them for http call.
This is achieved by setting the clientConnector with a HttpClient and his SslContext but we need to have access to the WebClient.Builder to do that, also adding filter (custom headers)
That's the purpose of this PR, use the work already done with default ObjectMapper and DateFormat to avoid having to do it and get access to webClient or webClientBuilder.
It also fix: #8602 (closed)