Uploaded image for project: 'Weld'
  1. Weld
  2. WELD-1710

weld-servlet detects tomcat container when used in jetty 9.2

XMLWordPrintable

    • Hide

      Deploy war with weld-servlet.jar in WEB-INF/lib to standalone jetty 9.2.2 (it supports servlet api 3.0, so org.jboss.weld.environment.servlet.EnhancedListener will be called automatically if web.xml has version 3.0+.

      Show
      Deploy war with weld-servlet.jar in WEB-INF/lib to standalone jetty 9.2.2 (it supports servlet api 3.0, so org.jboss.weld.environment.servlet.EnhancedListener will be called automatically if web.xml has version 3.0+.

      TomcatContainer use org.apache.tomcat.InstanceManager class to detect that container is Apache Tomcat but current Jetty (at least 9.2.2) contains this class in classpath (in jsp-engine lib/apache-jsp/org.mortbay.jasper.apache-jsp-8.0.3.v20140313.jar) so Jetty is false detected as Tomcat which leads to java.lang.NoClassDefFoundError: org/apache/catalina/core/ApplicationContextFacade later.

      To avoid this error TomcatContainer should use less generic class (e. g. org.apache.catalina.connector.Request or something similar).

              mkouba@redhat.com Martin Kouba
              grossws Konstantin Gribov (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: