fix(deps): update dependency jakarta.xml.bind:jakarta.xml.bind-api to v4

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
jakarta.xml.bind:jakarta.xml.bind-api	2.3.3 -> 4.0.2

---

Release Notes

jakartaee/jaxb-api (jakarta.xml.bind:jakarta.xml.bind-api)

v4.0.2: Jakarta XML Binding API 4.0.2

Compare Source

The 4.0.2 release is a bug fix release of 4.0.0.

Following changes are included:

• #​229 - Documented exception thrown is incorrect for javax.xml.bind.DatatypeConverter#print(Object) methods
• #​231 - Incorrect exception thrown by javax.xml.bind.DatatypeConverter
• #​236 - Fix the link to WS-I BP 1.0 in the spec
• #​284 - Re-use SAXParserFactory in AbstractUnmarshallerImpl for better performance
• Javadoc improvements - formatting, typos, grammar, sample code
• uses Jakarta Activation APIs 2.1.3

New Contributors

• @​antoniosanct made their first contribution in https://github.com/jakartaee/jaxb-api/pull/281

Full Changelog: jakartaee/jaxb-api@4.0.1...4.0.2

v4.0.1: Jakarta XML Binding API 4.0.1

Compare Source

The 4.0.1 release is a bug fix release of 4.0.0.

Following changes are included:

• #​240 - Fixes parseBoolean according spec
• #​273 - Allow usage of API jar on Android platform
• #​275 - Make sure providers get only properties they are required to understand
• #​276 - Add instructions for OSGi mediator
• uses Jakarta Activation APIs 2.1.2

New Contributors

• @​laurentschoelens made their first contribution in https://github.com/jakartaee/jaxb-api/pull/279

Full Changelog: jakartaee/jaxb-api@4.0.0...4.0.1

v4.0.0: Jakarta XML Binding API 4.0.0

Compare Source

The major release contains following changes:

• drops compatibility with JAXB 1.0
• removes constraints on using java.desktop/java.beans.Introspector
• removes deprecated jakarta.xml.bind.Validator
• removes deprecated jakarta.xml.bind.context.factory property
• drops implementation lookup through META-INF/services/jakarta.xml.bind.JAXBContext
• drops implementation lookup through jaxb.properties file
• adds implementation lookup through the properties Map passed to JAXBContext.newInstance(...) methods
• provided implementation of the DatatypeConverterInterface throws exception on invalid input

Project Board: https://github.com/eclipse-ee4j/jaxb-api/projects/1
Full Changelog: jakartaee/jaxb-api@3.0.0...4.0.0

v3.0.1: Jakarta XML Binding API 3.0.1

Compare Source

The 3.0.1 release is a bug fix release of 3.0.0.

Following changes are included:

• #​172 - Default factory class name changed
• Classloading related fixes
• uses Jakarta Activation APIs 2.0.1

v3.0.0: Jakarta XML Binding API 3.0.0 Final Release

Compare Source

The 3.0.0 release is the first release under the jakarta.xml.bind.* namespace.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Qodana Community for JVM

106 new problems were found

Inspection name	Severity	Problems
Usage of API marked for removal	🔴 Failure	2
@NotNull/@Nullable problems	🔶 Warning	38
Unchecked warning	🔶 Warning	32
'equals()' method which does not check class of parameter	🔶 Warning	21
Nullability and data flow problems	🔶 Warning	3
Field can be local	🔶 Warning	2
Declaration has problems in Javadoc references	🔶 Warning	2
AutoCloseable used without 'try'-with-resources	🔶 Warning	1
Class is exposed outside of its visibility scope	🔶 Warning	1
Javadoc declaration problems	🔶 Warning	1
Mismatched query and update of collection	🔶 Warning	1
Optional.get() is called without isPresent() check	🔶 Warning	1
Commented out code	◽️ Notice	1

☁️ View the detailed Qodana report

Contact Qodana team

Contact us at [email protected]

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions