Uploaded image for project: 'Spring Framework'
  1. Spring Framework
  2. SPR-10578

Revert change for SPR-10402 that allowed treating empty values as missing values

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Complete
    • Affects Version/s: 3.2.3
    • Fix Version/s: 3.2.4, 4.0 M2
    • Component/s: Web
    • Labels:
      None
    • Last commented by a User:
      true

      Description

      Today, I have downloaded Spring Framework 3.2.3.

      Now, handleMissingValue is called, even if the @RequestParam attribute required = false!

      IMHO, this new behaviour is suboptimal. We have many cases, where an empty string parameter value (which has been converted to null by the property editor) should not be handled as missing parameter (even if required = true)! And I guess that many others who relied on the prior behaviour will be confused, too.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                rstoya05-aop Rossen Stoyanchev
                Reporter:
                ihr-staal Alfred Staflinger
                Last updater:
                Spring Issuemaster
              • Votes:
                6 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Days since last comment:
                  40 weeks, 1 day ago