-
Notifications
You must be signed in to change notification settings - Fork 563
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
UnsupportedOperationException from AwsServletContext.getNamedDispatcher #499
Comments
You are right, |
If
then the stacktrace looks like
so it seems like there is an infinite loop and that the
so it will not use the servlet name stored in |
The biggest problem seems to be the lack of servlet support. With these hacks, I was able to at least get the servlet deployed and one request to go through main...Artur-:aws-serverless-java-container:main |
Thanks for the feedback. Yes, the implementation is not complete. We wouldn't pass the TCK but it's sufficient for most of the use cases. Would you mind adding a few test cases and opening a PR? I'm happy to merge the changes and include them in the next release. |
I will do that once I get everything working first (unless I forget..) |
Serverless Java Container version:
1.9.1
Implementations:
Spring Boot 2
Framework version:
SpringBoot 2.7.5
Frontend service:
HTTP API
Deployment method:
SAM
Scenario
Trying to get a https://hilla.dev/ Spring Boot 2 application up and running
Expected behavior
A request to the application ends up in the deployed servlet
Actual behavior
Every request fails with
This originates in
ServletForwardingController
which doesAm I holding it wrong as it seems this can never work as
getNamedDispatcher
inAwsServletContext
always throws an exception?Steps to reproduce
Example project is at https://github.com/Artur-/hilla-react-lambda
Full log output
The text was updated successfully, but these errors were encountered: