Closed artur1211 closed 8 months ago
We appreciate your feedback and we are currently reviewing this. We will update as soon as we have more information about next steps.
Hi, I am also facing the same issue. When can we expect the fix!!
Any progress on the issue? Is there a workaround?
I have updated my pom.xml to include the 11.x.x version instead of 12.x.x and scope to test. As I was using only for local testing and it worked for me.
Hi, we currently have this planned in our issues backlog. We do not have an ETA, but it is being prioritized. We will provide a status update once this is in progress.
Facing the same issue as well
Is there a workaround?
An alternative way to obtain a mock client that does not use HTTP connections at all (so methods like com.amazonaws.AmazonWebServiceResult#getSdkHttpMetadata
return null
):
AmazonDynamoDB amazonDynamoDB = DynamoDBEmbedded.create().amazonDynamoDB();
Hi, we are facing the same issue. Any ETA of the fix would help a lot. Thanks!
Same here. is there any active work for this ? Thank you
Same here. We had to upgrade our Spring Boot to 3.2+ to resolve a vulnerability and we encountered this. Any idea when this will be worked? :)
Hello Customers,
@artur1211 @ssanganbatte @marat-aukhadiev-andsafe @harrydhillon43 @klach-ocado @psiman-wandera @esagardia @chris-tuncap
The DynamoDB DevEx team is continuously making improvements to DynamoDB local. As we have received feedback from you as a user of DynamoDB local as a Maven dependency. Our latest improvement to DynamoDB local is an upgrade to Jetty 12 to be compatible with Spring Boot 3.2.0. We are reaching out to you to see if you would like to participate in the early testing of our DynamoDB local beta version, which includes this upgrade. We would really appreciate your support as your participation will help us ensure high quality user experience with this upgrade before we launch to the general public.
If you would like to participate in early testing of our DynamoDB local beta release, please send us an email at: aws-ddblocal-feedback@amazon.com.
Regards, The DynamoDB DevEx Team
Today, we are excited to announce that DynamoDB local for Amazon DynamoDB upgrades to Jetty 12 and JDK 17. We recommend that you run the latest version (2.3.0) of DynamoDB local to utilize the most recent updates and features of DynamoDB local for your development and testing use cases.
https://aws.amazon.com/about-aws/whats-new/2024/03/amazon-dynamodb-local-upgrades-jetty-12-jdk-17/
@shetsa-amzn thanks for quick fix of this issue 👏
Today, we are excited to announce that DynamoDB local for Amazon DynamoDB upgrades to Jetty 12 and JDK 17. We recommend that you run the latest version (2.3.0) of DynamoDB local to utilize the most recent updates and features of DynamoDB local for your development and testing use cases.
https://aws.amazon.com/about-aws/whats-new/2024/03/amazon-dynamodb-local-upgrades-jetty-12-jdk-17/
There is an incompatibility between jetty versions in the upcoming Spring Boot 3.2 (it brings 12.0.1 jetty with it) and DynamoDB Local 2.0.0 (contains jetty in version 11.0.15). When one tries to run DynamoDB Local on the jetty (12.0.1) taken from Spring Boot 3.2 it leads to the following exception:
It would be great if you could update Jetty to 12.0.1 (Spring Boot 3.2 version)