Hi All, We're trying to upgrade from dropwizard-0.9.1 to dropwizard-1.0.0 and are seeing the following change in behaviour.
We have a Jersey resource configured to take a model object as a parameter which has a field which is specified as @NotEmpty. With 0.9.1 we get the following exception thrown when the field is empty: "The request entity had the following errors: metrics may not be empty." With 1.0.0 we now see: " post.arg0.metrics may not be empty." Is this a hibernate-validator-4.x vs. hibernate-validator-5.x regression? Anybody have any ideas how we can address this issue? Thanks, Frank Grimes -- You received this message because you are subscribed to the Google Groups "dropwizard-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
