-
Notifications
You must be signed in to change notification settings - Fork 560
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
Provide Spring Boot 3 support #487
Comments
Hi Gareth, |
If you come across this issue and you'd like to see it implemented, please +1 here or reach out privately to me or your AWS account team. The more customers requesting it, the easier it is for us to prioritize it. |
If you are looking to run Spring Boot 3 on Lambda before we finish the work on this issue, this sample may be helpful for you: https://github.com/maschnetwork/aws-lambda-spring-boot-3 |
Thanks for this. I do have a Spring Boot 3 Lambda deployment working, but will review this and see if it can be improved based on the sample you've supplied. |
@garethpowell Can you kindly share a repo containing a demo of how you achieved this? I'm actively looking to convert at least a few parts of my Spring Boot 3 app to serverless. Thanks in advance! |
We need Spring boot 3 support for AWS Java serverless container library and please advise how soon this will be available |
+1 |
This would be nice for several reasons ranging from "You should not start new apps on Spring Boot 2 as it reasonably soon reaches end of life" to "Spring Boot 3 has support for native compilation which combined with lambda could be super great" |
Hi, I am also waiting for SpringBoot3 support. Looking forward to it :) |
+999 Any way for the humble spring developer to support this other than upvoting? |
Appreciate your interest. If you know your AWS account team, please talk to them about it to make sure they influence the related feature requests internally for you. We are actively working on additional support for this project. Of course pull requests are welcome as well. Another contributor already started working on #478 with a focus on Jersey but Jakarta EE is a prerequisite for Spring Boot 3 too. In addition Spring Boot 3 requires Java 17 so we are also dependent on aws/aws-lambda-base-images#29. |
+1. I would like support for spring boot 3 also. Starting a green field project so I want use Spring boot 3 instead of 2. |
We are also eager to upgrade to SB3! |
We are depending on a commons-fileupload release which is unfortunately not yet available (https://issues.apache.org/jira/browse/FILEUPLOAD-309). However to not further delay a release we are thinking to provide a 2.0.0-M1 version very soon. Until then feel free to build a SNAPSHOT version on your own and provide feedback. |
2.0.0-M1 (without commons-fileupload support) is now available on Maven Central. |
I can't find 2.0.0-M1 on Maven central. A link would be appreciated. |
To help us debug your issue fill in the basic information below using the options provided
Serverless Java Container version: 1.9
Framework version: SpringBoot 3.0.0
Scenario
We would like to be able to use Spring Boot 3 in our Lambda development.
Expected behavior
To fully support Spring Boot 3
Actual behavior
Due to the
javax
tojakarta
namespace/package change in JakartaEE and associated Spring Boot 3 use, the current aws-serverless-java-container does not startup.Steps to reproduce
Deploy a Spring Boot 3 Lambda using the
com.amazonaws.serverless:aws-serverless-java-container-springboot2:1.9
into AWS SAM localFull log output
Paste the full log output from the Lambda function's CloudWatch logs
Please note that in the short term, I've forked this project and migrated the code to support Spring Boot 3. It's far from optimal and some functionality is disabled or left unimplemented. It serves our needs for the moment, but we switch to an official Spring Boot 3 version when you have it ready.
The text was updated successfully, but these errors were encountered: