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

Duplicated ConstraintViolation message

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 19.0.0.Final
    • 17.0.1.Final, 18.0.0.Beta1
    • Bean Validation, REST
    • None
    • Hide
      1. Send an invalid request -> only one violation
      2. Send a valid request -> correct response
      3. Send an invalid request -> violation is duplicated
      4. Send an invalid request -> only one violation

      The attached example project has this included as Testcase.

      Show
      Send an invalid request -> only one violation Send a valid request -> correct response Send an invalid request -> violation is duplicated Send an invalid request -> only one violation The attached example project has this included as Testcase.

    Description

      We currently are upgrading our application from Wildfly 13 to Wildfly 17.0.1 and are receiving duplicated constraint violations in the response of an invalid request.

      Interestingly Wildfly 13 also seems to be not behaving correctly on the third request but in another way. There is the violation exception returned in the response instead of the duplicated value Wildfly 17 is returning now.

      I also tested this on the currently available Wildfly 18 Beta 1 and the issue is also reproducible.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. RESTEASY-2358 Duplicated ConstraintViolation message

          • 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. EJBCLIENT-357 EJBClient.isEJBProxy method returns false when testing an ejb proxy

          • 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

              rsigal@redhat.com Ronald Sigal
              rschimpf Robin Schimpf (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: