This repository was archived by the owner on Mar 4, 2021. It is now read-only.
Explicitly setting servlet load order in web.xml so that Tomcat behaves the same as Jetty #54
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
It looks like the problem we had with tomcat was related to the load-on-startup parameter used in web.xml.Because it's up to the servlet container (Jetty or Tomcat) which order it loads servlets that have the same value, we noticed the following variation on loading:
Jetty: 1. Monkey Server, 2. jersey-servlet
Tomcat: 1. jersey-servlet , 2. Monkey Server
So we explicitly set a larger number for jersey-servlet to ensure same load order in Tomcat as in Jetty. For details on load order, see snippet from servlet 2.5 specification at the bottom of this post.
Fixed web.xml
Servlet 2.5 Specification snippet