-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Comments
Hi @MasatoshiTada yes, currently the SDK only supports 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 Thank you for your comment!
Do you have any plan to support jakarta.* namespaces in SDK v2?👀 |
Still no news on this issue? |
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. |
Indeed, migration to sdk v2 works like a charm |
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:
|
This issue is now closed. Comments on closed issues are hard for our team to see. |
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) ofjakarta.xml.bind:jakarta.xml.bind-api
andcom.sun.xml.bind:jaxb-api
. But unfortunately, I still see the WARN log above.I changed versions from
3.0.0
to2.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
The text was updated successfully, but these errors were encountered: