Spring Framework
  1. Spring Framework
  2. SPR-7062

Add Group Class support to JSR-303 Validation using @Valid

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Web
    • Labels:
      None

      Description

      Would like a replacement for @Valid that could take group classes for JSR-303 validation. Right now only the default group class of JSR-303 Constraints is run for the @Valid.

      Please refer to this forum thread for more detail: http://forum.springsource.org/showthread.php?p=292566

        Issue Links

          Activity

          Hide
          recoco zhang added a comment -

          Anticipate this feature.
          Now if I use @Valid with JSR-303 Constraints group , Spring cant binding failure messages to BindingResult. If only @Valid with Default group, Spring can binding failure messages to BindingResult.
          So for the complex situation such as a create controller and a update controller which have different constraints group, it's very inconvenient.

          Show
          recoco zhang added a comment - Anticipate this feature. Now if I use @Valid with JSR-303 Constraints group , Spring cant binding failure messages to BindingResult. If only @Valid with Default group, Spring can binding failure messages to BindingResult. So for the complex situation such as a create controller and a update controller which have different constraints group, it's very inconvenient.
          Hide
          Giljae Joo(주길재) added a comment -
          Show
          Giljae Joo(주길재) added a comment - Reference is http://giljae.com/blog/13090537

            People

            • Assignee:
              Juergen Hoeller
              Reporter:
              Jon Daly
              Last updater:
              Trevor Marshall
            • Votes:
              18 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Days since last comment:
                2 years, 37 weeks, 2 days ago