Uploaded image for project: 'Application Server 3 4 5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-7106

Deployment Based On An EAR's application.xml Order No Longer Works

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 6.0.0.M1
    • None
    • Deployers
    • None

    Description

      During deployment, even though <module-order>strict</module-order> is specified in jboss-app.xml, the EAR deployer still deploys in alphabetical order.

      Attachments

        Issue Links

          is blocked by

          Feature Request - Feature requests from customers and/or users JBMETA-221 Add complete support for module-order

          • 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 incorporated by

          Feature Request - Feature requests from customers and/or users JBPAPP-1740 JBoss 5 Migration: deployer still deploys in alphabetical order

          • 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
          relates to

          Sub-task - The sub-task of the issue JBAS-7514 Merge JBAS-7106 to trunk

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-5891 Deployment Based On An EAR's application.xml Order No Longer Works

          • 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

              jgreene@redhat.com Jason Greene
              rhn-support-jawilson Jimmy Wilson
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: