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

weld-servlet detects tomcat container when used in jetty 9.2

    XMLWordPrintable

Details

    • 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+.

    Description

      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).

      Attachments

        Issue Links

          is related to

          Task - Represents a small unit of work that is not end-user facing. WELD-2236 Document the usage of org.jboss.weld.environment.container.class init param

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          relates to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) WELD-2235 Avoid nasty stacktrace when

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: