[tokenizationwebhooks] Code generation: update services and models

[AdyenAutomationBot]

This PR contains the automated changes for the tokenizationwebhooks service.

The commit history of this PR reflects the adyen-openapi commits that have been applied.

[gemini-code-assist]

Summary of Changes

Hello @AdyenAutomationBot, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request delivers an automated update to the tokenizationwebhooks service, primarily focusing on code generation aspects. The changes are largely cosmetic, involving the reordering of imports, the addition of specific Jackson annotations for serialization/deserialization, and general code formatting improvements across various model and handler files. These updates ensure the generated code adheres to the latest standards without altering the core business logic or functionality of the tokenization webhooks.

Highlights

• Automated Code Generation Update: The pull request consists of automated updates to the tokenizationwebhooks service, aligning with recent adyen-openapi commits.
• Import Reorganization: Imports across multiple Java model and handler files have been reordered and some new Jackson annotations added, likely due to updated code generation standards.
• Code Formatting Enhancements: Minor formatting adjustments, including whitespace, newlines, and comment styles, have been applied to improve code consistency and readability.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request contains automated changes from a code generator, primarily focused on updating services and models for tokenizationwebhooks. The changes are mostly stylistic, including adjustments to indentation, Javadoc formatting, import ordering, and newlines. I've reviewed the changes and found one minor point of improvement for code consistency in JSON.java. Otherwise, the changes look good and don't introduce any functional issues.

[gemini-code-assist]

For consistency and improved readability, it's better to use the diamond operator <> for type inference, which is available since Java 7. This is already used for modelDescendants in this same file.

Suggested change

	private static final Map<Class<?>, ClassDiscriminatorMapping> modelDiscriminators = new HashMap<Class<?>, ClassDiscriminatorMapping>();
	private static final Map<Class<?>, ClassDiscriminatorMapping> modelDiscriminators = new HashMap<>();