OF-2717: Remove JasperInitializer from BOSH context

Earlier commits for this issue have removed the same initializer elsewhere. See mailinglist thread starting at https://www.eclipse.org/lists/jetty-users/msg10880.html
igniterealtime · Mar 10, 2025 · 2bc24a9 · 2bc24a9
1 parent b544064
commit 2bc24a9
Showing 1 changed file with 0 additions and 3 deletions.
diff --git a/xmppserver/src/main/java/org/jivesoftware/openfire/http/HttpBindManager.java b/xmppserver/src/main/java/org/jivesoftware/openfire/http/HttpBindManager.java
@@ -18,7 +18,6 @@
 
 import org.apache.tomcat.InstanceManager;
 import org.apache.tomcat.SimpleInstanceManager;
-import org.eclipse.jetty.ee8.apache.jsp.JettyJasperInitializer;
 import org.eclipse.jetty.ee8.nested.ContextHandler;
 import org.eclipse.jetty.http.HttpHeader;
 import org.eclipse.jetty.http.HttpMethod;
@@ -669,8 +668,6 @@ protected ServletContextHandler createBoshHandler()
         final int options = ServletContextHandler.SESSIONS;
         final ServletContextHandler context = new ServletContextHandler( null, "/http-bind", options );
 
-        // Ensure the JSP engine is initialized correctly (in order to be able to cope with Tomcat/Jasper precompiled JSPs).
-        context.addServletContainerInitializer(new JettyJasperInitializer());
         context.setAttribute( InstanceManager.class.getName(), new SimpleInstanceManager() );
 
         // Generic configuration of the context.