Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-364

a "failure-causes-rollback="false"" attribute for the filesystem scanner

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 8.0.0.CR1
    • None
    • Management
    • None

    Description

      JBIDE-11509, AS7-783 and TORQUE-576 all talk about the problem of all deployments found at startup is deployed in one operation and if one deployment fails all is rolled back resulting in some rather bad usability issues - especially at development time, but even also at production time for those using file deployments.

      Suggestion on irc was that there could be an option on the file scanner (possibly false by default?) to say that failure causes rollback.

      Individual deployments could then still fail, but at least not everything would be rolledback and it would still allow proper interdependent deployments to work.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-11509 Starting the AS/EAP when it already has multiple projects deployed

          • 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

          Task - Represents a small unit of work that is not end-user facing. AS7-783 Deployment scanner service should use a separate operation for each deployment

          • 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. WFCORE-2876 runtime-failure-causes-rollback does not seem to have effect when configured in model

          • 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

          Activity

            People

              emuckenhuber_jira Emanuel Muckenhuber (Inactive)
              manderse@redhat.com Max Andersen
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: