-
Notifications
You must be signed in to change notification settings - Fork 762
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 Tomcat 10.1.x for REST API #4075
Comments
Comparing |
Tomcat 10.1 uses jakarta.servlet-api 6.0 while Tomcat 10.0 uses 5.0. The removal of deprecated APIs in jakarta.servlet-api happened via jakartaee/servlet#419 (for 6.0.0). |
For the record, with Tomcat 10.1, the webapp seems to work normally in terms of the UI. That is after after the fix for #4050. |
For me this seems to also prevent the initial sync/indexing. I've tried the latest and master docker images, log from the master follows:
1.7.35 seems to be working more or less fine and when I perform the initial index with it, the latest/master seems to be able to display what's already indexed. |
Thanks for the report, will constrain Tomcat to 10.0 for the Docker images for now. Also, the failures make sense as the indexer and related tooling rely on the RESTful APIs a lot. |
I have a feature branch with some of the necessary changes, however it currently suffers from something similar to eclipse-ee4j/jersey#4617 |
Also, Jersey does not seem to be ready for the new servlet-api (eclipse-ee4j/jersey#5181) so this is on hold. |
Jersey 3.1.0 was released so this part is unblocked. |
eventually fixes oracle#4075
As discussed in #4070 , API search request in Tomcat 10.1.0 ends with:
The text was updated successfully, but these errors were encountered: