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

Newly added InfiniteOrPositiveValidators to messaging attributes should just print warning if negative values are not -1

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 12.0.0.CR1, 12.0.0.Final
    • 12.0.0.Beta1
    • JMS
    • None
    • Migration

    Description

      This Jira is reaction to WFLY-9433.

      The WFLY-9433 makes validator rules more strict for some attributes in messaging subsystem. Although there is no reason to use these values (which are newly considered as invalid), it was possible to configure them and they worked with Wildfly 11 and previous releases.

      As it is proposed in JBEAP-14110, this change should be done in 2 steps:

      • only WARN the user if the parameter is not valid (a negative value other than -1)
      • in next release, reject the parameter

      I am setting priority as Blocker, because this fix must be included in Wildfly 12 release. It makes no sense to do it later.

      Attachments

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-3651 ParameterCorrector are not taken into account by XML parser

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

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-14110 Apply InfiniteOrPositiveValidators to messaging attributes allow valid value -1

          • 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

          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) WFLY-9433 Apply InfiniteOrPositiveValidators to messaging attributes allow valid value -1

          • 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

              jmesnil1@redhat.com Jeff Mesnil
              eduda_jira Erich Duda (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: