In the very latest 0.8.6-SNAPSHOT, you can get JSR 303 validation working. Here is a sample controller:

@RestController
@RequestMapping(value = "/api/person")
@Api(value = "Person")
public class PersonController {

@RequestMapping(value = {"/blah"}, method = POST, produces = APPLICATION_JSON_VALUE)
@ApiOperation(value = "Creates and returns a Person",
notes="Populates a Person instance using the data supplied in the posted form fields")
public PersonResponse createPerson(
        @ModelAttribute @Valid
        final PersonForm person, final BindingResult result) {

    if (result.hasErrors()) {
        ...
    }
    return null;
}

}

How does the Person looks like in your example?
We cannot confirm it is working (version 0.8.8)
We still need to add a manual swagger annotation to make it work like:

import javax.validation.constraints.NotNull;
import com.wordnik.swagger.annotations.ApiModelProperty;
class Person {
      @NotNull
      @ApiModelProperty(required = true)
      private String foo;
}

It would be nice if it could handle this not only in the model, but for Query, Path, Matrix params as well. Also, it would nice if it would handle more than @NotNull and could handle the other annotations as part of the spec. See http://docs.oracle.com/javaee/7/api/javax/validation/constraints/package-summary.html

Then, the clients of the swagger spec, such as the swagger-ui could validate the fields as they are entered without needing to make a call to the server.

Relates to this issue: #311

As far as I can tell none of the JSR-303 constraint's are supported by springfox (including @NotNull).
It should be relatively straight forward to offer rudimentary support for these constraints but we would have to provide a way to disable the feature because there are scenarios, such as using groups to conditionally apply validation rules based on runtime conditions, where it is not feasible to try to infer validation constraints.

@jasonchaffee would you be interesting in contributing to your idea?

I prefer this to be separate module springfox-validations. Should be simple enough to use the plugin models to enrich the service descriptions.

Don't want it to be a concern in the core modules, just because it can be released incrementally and possibly out-of-band.

I agree that it makes sense to be in a separate module.

On Apr 13, 2015, at 5:04 PM, Dilip Krishnan notifications@github.com wrote:

I prefer this to be separate module springfox-validations. Should be simple enough to use the plugin models to enrich the service descriptions.

Don't want it to be a concern in the core modules, just because it can be released incrementally and possibly out-of-band.

—
Reply to this email directly or view it on GitHub #356 (comment).

If I can get some extra time I can take a stab at it. It isn’t a high priority for our use right now, so that might limit the time I will have to look into it. If that were to change, I would definitely take it on.

On Apr 13, 2015, at 4:53 PM, Adrian Kelly notifications@github.com wrote:

Relates to this issue: #311 #311
As far as I can tell none of the JSR-303 constraint's are supported by springfox (including @NotNull https://github.com/NotNull).
It should be relatively straight forward to offer rudimentary support for these constraints but we would have to provide a way to disable the feature because there are scenarios, such as using groups https://docs.jboss.org/hibernate/validator/4.0.1/reference/en/html_single/#validator-usingvalidator-validationgroups to conditionally apply validation rules based on runtime conditions, where it is not feasible to try to infer validation constraints.

@jasonchaffee https://github.com/jasonchaffee would you be interesting in contributing to your idea?

—
Reply to this email directly or view it on GitHub #356 (comment).

is the support for JSR-303 (Java Bean Validation) available ?

I added a sample implementation of NotNull and Min/Max to issue #987.

As of PR #1159 the annotations @NotNull, @min, @max, @SiZe are supported.

Open questions:

• Please let me know if I also should add support for the @Email (resolving to type "string").
• Pls also let me know what is the best way to add test cases for this in the petstore?
  (where should I put them?)
• The max-value "infinity" is currently not correctly dealt with, if it is the usage of the MAX-values of Integer/Double could be replaced with infinity (commented in BeanvalidationModelPropertyBuilderPlugin)