Uploaded image for project: 'Application Server 7'
  1. Application Server 7
  2. AS7-2119

Portable war: Weld deployment on JBoss AS 7 should not require to remove the WeldListener line from the web.xml

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Critical
    • 7.1.0.Beta1
    • 7.1.0.Alpha1
    • None
    • None

    Description

      When deploying on JBoss AS 7, the web.xml can't contain this:

        <listener>
    <listener-class&gt;org.jboss.weld.environment.servlet.Listener</listener-class&gt;
  </listener>

      When deploying on any other app servers (JBoss AS 5.1 EAP, Tomcat 6, Jetty 6, ...) that code needs to be there.
      This makes for an unportable wars.

      Maven profiles cannot fix this in many cases:

      • You don't want to run your build 5 times to build 5 different wars. You run it once, build a generic war and use assembly descriptors to build 5 appserver specific wars from that.
      • When you're using GWT, you want run in GWT-hosted mode (which uses jetty 6) a lot. So the default web.xml needs to contain it.
      • When you're using arquillian-jboss7 (in maven and straight for your IDE), the default web.xml should not have it.
      • When you're deploying a generic war to nexus, the web.xml should contain it?

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users WELD-984 Weld should not require application server specific changes to a war

          • 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
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WELD-979 Weld 1.1.3-SNAPSHOT and 1.1.2.AS7 fail on JBoss AS 7 with FileNotFoundException on an existing file

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved
          is duplicated by

          Feature Request - Feature requests from customers and/or users WELD-718 register Weld Servlet listener in web fragment

          • 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.
          • Closed
          is related to

          Feature Request - Feature requests from customers and/or users WELD-985 Make Tomcat 6 and Jetty 6 and 7 specific configuration obsolete

          • 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

          Bug - A problem that impairs or prevents the functions of the product. RESTEASY-740 Portable wars: a war using RESTEasy should deploy to deploy jboss AS 7 and Tomcat without modifcation: it should not require to remove the WEB-INF/lib/resteasy-*.jar files on JBoss AS 7

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

          Activity

            People

              sdouglas1@redhat.com Stuart Douglas
              gdesmet@redhat.com Geoffrey De Smet (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: