Jetty 11 Doesn’t Detect Servlets

by

Jetty 11 is based on Jakarta Servlet 5.0, which is part of Jakarta EE 9.

Jakarta EE 9 underwent the “big bang” change (their name, not mine) to namespace and packaging, there is no longer a javax.servlet.* it is now jakarta.servlet.*.

There is literally nothing in Jetty 11 that looks for javax.servlet.*.

Some quick history …

  • Oracle owned Java EE.
  • Oracle produced Java EE 7.
  • Oracle decided it didn’t want to create/manage EE anymore.
  • Oracle gave all of EE to the Eclipse Foundation.
  • Oracle did not grant the Eclipse Foundation the right to use “java” or “javax” in this new EE reality.
  • Eclipse Foundation renamed it to “Jakarta EE” for legal reasons.
  • Eclipse Foundation releases “Jakarta EE 8” which is essentially just “Java EE 7” renamed for legal reasons (no package namespace change yet)
  • Eclipse Foundation renamed all packaging from javax.<spec> to jakarta.<spec> for legal reasons.
  • Eclipse Foundation releases “Jakarta EE 9” which is essentially just “Jakarta EE 8” but with a namespace change (this is the “big bang” mentioned above)

(be aware, I skimmed over a lot of other things that happened between these steps)

javax.servlet.* is dead, long live jakarta.servlet.*.

Jetty maintains the following versions (currently)

Jetty Servlet EE Namespace
Jetty 10.x Servlet 4.0 Jakarta EE 8 javax.servlet
Jetty 11.x Servlet 5.0 Jakarta EE 9 jakarta.servlet

There is no backward compatibility feature to allow both javax.servlet and jakarta.servlet to coexist in a release of Jetty. (we’ve tried this a few times, the complexity of the Servlet spec makes this very difficult for the HttpSession, RequestDispatcher, Dynamic servlet/filter registrations, etc). Jetty is working with the Servlet spec in Servlet 6.0 to attempt to address these concerns. A single release of Jetty supporting both namespaces is not likely until Jetty 12.

For now, the best we can hope for (and there are several projects started to do this, all alpha quality ATM) is some kind of tooling that updates your jars and/or source for the new packaging in an automated fashion to then be run on a Jakarta based server.

More Related Contents:

  1. Serving static files from alternate path in embedded Jetty
  2. The method getDispatcherType() is undefined for the type HttpServletRequest
  3. Is there a way to pass JVM args via command line to Maven? [duplicate]
  4. Why is HttpServletRequest inputstream empty?
  5. Tomcat VS Jetty [closed]
  6. GSON is not being imported into the maven project
  7. How do I load a file from resource folder?
  8. Calling a servlet from JSP file on page load
  9. How do you return a JSON object from a Java Servlet
  10. What is recommended way for spawning threads from a servlet in Tomcat
  11. Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize
  12. How do I keep a user logged into my site for months?
  14. How can I get client information such as OS and browser
  15. How to build a docker container for a Java application
  16. maven. lambda expressions are not supported in -source 1.5
  17. How can I get the HTTP status code out of a ServletResponse in a ServletFilter?
  18. How to implement pagination in Spring MVC 3 [closed]
  19. Build order of Maven multimodule project?
  20. Is there a url rewriting engine for Tomcat/Java?
  21. Spring MVC using tomcat, maven and intelliJ Error [duplicate]
  22. Access maven properties defined in the pom
  23. Using Maven to download dependencies to a directory on the command line
  24. How do you organize tests in a modular Java project?
  25. How can I store state for an individual browser tab/window?
  26. “java.lang.OutOfMemoryError: PermGen space” in Maven build [duplicate]
  27. get rid of POM not found warning for org.eclipse.m2e:lifecycle-mapping
  28. Difference between the maven-assembly-plugin, maven-jar-plugin and maven-shade-plugin?
  29. Proper fix for Java 10 complaining about illegal reflection access by jaxb-impl 2.3.0?
  30. Maven- No plugin found for prefix ‘spring-boot’ in the current project and in the plugin groups

Leave a Comment