Uploaded image for project: 'RESTEasy'
  1. RESTEasy
  2. RESTEASY-1459

Method being executed although validation fails

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 3.1.0.Final, 3.0.20.Final
    • None
    • None
    • None
    • Hide
      1. Post valid message to test-validation-1.0-SNAPSHOT/testreq/send 
        {
    "test": "1",
    "path":"da"
}
      2. Post invalid message to test-validation-1.0-SNAPSHOT/testreq/send 
        {

}
      3. Look at server log -> one 'nevertheless' from the positive call
      4. Post valid message to test-validation-1.0-SNAPSHOT/testapp/send 
        {
    "test": "1",
    "path":"da"
}
      5. Post invalid message to test-validation-1.0-SNAPSHOT/testapp/send 
        {

}
      6. Look at server log -> 'nevertheless' log from both calls

      -> Method is being called although validation fails but only on applicationscoped bean
      NOTE: It only seems to happen if at least one call was successfull

      Show
      Post valid message to test-validation-1.0-SNAPSHOT/testreq/send { "test" : "1" , "path" : "da" } Post invalid message to test-validation-1.0-SNAPSHOT/testreq/send { } Look at server log -> one 'nevertheless' from the positive call Post valid message to test-validation-1.0-SNAPSHOT/testapp/send { "test" : "1" , "path" : "da" } Post invalid message to test-validation-1.0-SNAPSHOT/testapp/send { } Look at server log -> 'nevertheless' log from both calls -> Method is being called although validation fails but only on applicationscoped bean NOTE: It only seems to happen if at least one call was successfull

    Description

      See test-validation.zip and steps to reproduce
      There are 2 rest services included one with an ApplicationScoped and one with a RequestScoped implementation. They behave differently with regard to validation.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. RESTEASY-2503 After first invocation on an EJB, class/field/property constraints don't get checked

          • 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
              davelane_jira David Lane (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: