Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support jakarta.* namespaces #2527

Closed
MasatoshiTada opened this issue Mar 14, 2021 · 7 comments
Closed

Support jakarta.* namespaces #2527

MasatoshiTada opened this issue Mar 14, 2021 · 7 comments
Labels
feature-request A feature should be added or improved.

Comments

@MasatoshiTada
Copy link

MasatoshiTada commented Mar 14, 2021

Describe the Feature

When I call AmazonS3#putObject() , I can see a WARN log below:

JAXB is unavailable. Will fallback to SDK implementation which may be less performant

So I added dependencies of 3.0.0 (this version is the latest) of jakarta.xml.bind:jakarta.xml.bind-api and com.sun.xml.bind:jaxb-api . But unfortunately, I still see the WARN log above.

I changed versions from 3.0.0 to 2.3.3 , and the WARN log was disappered.

It seems that aws-sdk-java doesn't support jakarta.* namespaces.

Is your Feature Request related to a problem?

At this time, this is not a very big problem. But it becomes bigger with the lapse of time.

Proposed Solution

Describe alternatives you've considered

As I mentioned above, use 2.3.3 . And if you use JDK 8, this problem doesn't occur.

Additional Context

Your Environment

  • AWS Java SDK version used: 1.11.327
  • JDK version used: 11
  • Operating System and version: macOS Big Sur 11.2.3 (M1)
@MasatoshiTada MasatoshiTada added feature-request A feature should be added or improved. needs-triage This issue or PR still needs to be triaged. labels Mar 14, 2021
@debora-ito
Copy link
Member

Hi @MasatoshiTada yes, currently the SDK only supports javax.xml.bind:jaxb-api, to work around the issue you can add the lib as a dependency. Marking as a feature request.

Please note that as the team's focus is in SDK v2 work, we don't have a timeline for when this will be prioritized.

@debora-ito debora-ito removed the needs-triage This issue or PR still needs to be triaged. label Mar 22, 2021
@MasatoshiTada
Copy link
Author

@debora-ito Thank you for your comment!

Please note that as the team's focus is in SDK v2 work, we don't have a timeline for when this will be prioritized.

Do you have any plan to support jakarta.* namespaces in SDK v2?👀

@antechrestos
Copy link

Still no news on this issue?

@debora-ito
Copy link
Member

@MasatoshiTada

I believe we don't use any package in SDK v2 that requires migrating to jakarta namespaces. If you are seeing otherwise, please share your dependency tree.

@antechrestos
Copy link

Indeed, migration to sdk v2 works like a charm

@debora-ito
Copy link
Member

We don't have plans to support this in v1, so I'll go ahead and close this issue.

This issue is not present in v2, please migrate to v2 for the improved performance and continued support from aws.

Reference:

  • Announcing end-of-support for AWS SDK for Java v1.x effective December 31, 2025 - blog post

@debora-ito debora-ito closed this as not planned Won't fix, can't repro, duplicate, stale Jul 23, 2024
Copy link

This issue is now closed.

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request A feature should be added or improved.
Projects
None yet
Development

No branches or pull requests

3 participants