Hi, On SO [1], a user asked whether it's possible to report custom names for property constraint violations, e.g. "nm" as retrieved from the annotation in this case: @JsonProperty("nm") @NotNull final public String name; At the moment that's not possible with HV, but one might think about a contract similar to ParameterNameProvider which returns the reported names for properties (or even custom names to be used instead of the constants "<return-value>" and "<cross-parameter>"). It's the first time I came across this requirement but adding support for this should not be too complex and it might be helpful to some. Any thoughts? --Gunnar [1] http://stackoverflow.com/questions/18878868/hibernate-validator-and-jacks... _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

Seems to me like a very specific use case. I guess we could offer a contract as you suggest, but it is not high on my priority list. Worth creating a Jira issue for though. --Hardy On 19 Jan 2013, at 9:05 AM, Gunnar Morling <gunnar(a)hibernate.org&gt; wrote: > Hi, > > On SO [1], a user asked whether it's possible to report custom names for > property constraint violations, e.g. "nm" as retrieved from the annotation > in this case: > > @JsonProperty("nm") > @NotNull > final public String name; > > At the moment that's not possible with HV, but one might think about a > contract similar to ParameterNameProvider which returns the reported names > for properties (or even custom names to be used instead of the constants > "<return-value>" and "<cross-parameter>"). > > It's the first time I came across this requirement but adding support for > this should not be too complex and it might be helpful to some. Any > thoughts? > > --Gunnar > > [1] > http://stackoverflow.com/questions/18878868/hibernate-validator-and-jacks... > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev

I also think that the conversion of the ConstraintViolation(s) into another format is more in the responsibility of the integrating technology. Taking JAX-RS/Resteasy as example, it will transparently convert any constraint violation objects into an equivalent XML or JSON response. Provided we return the wished property name in the reported violation, Resteasy's conversion would take over from there. 2013/9/19 Hardy Ferentschik <hardy(a)hibernate.org&gt; > > On 19 Jan 2013, at 9:44 AM, Emmanuel Bernard <emmanuel(a)hibernate.org&gt; > wrote: > > > It seems that what this user really needs is a way to convert the > Set<ConstraintViolation> into another format entirely, JSON in this case. I > wonder if we could find a more generic approach than just the ability to > change properties names. > > Well, there are really two problems. First the creation of the JSON format > and then the property name "conversion". I think they need to be addressed > separately. Even if we had/offered something to convert the constraint > violations, we still > would report the actual property name. > > In the described use case I would write the conversion code myself. The > constraint violation contains all the information needed to create the JSON > format and do the name conversion. It should not be hard to write. > > --Hardy > > > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

But then the JSON binding technology should be responsible for the property anme conversion too, right? After all that is the layer that does this change.

On Thu 2013-09-19 10:35, Gunnar Morling wrote: > I also think that the conversion of the ConstraintViolation(s) into another > format is more in the responsibility of the integrating technology. > > Taking JAX-RS/Resteasy as example, it will transparently convert any > constraint violation objects into an equivalent XML or JSON response. > Provided we return the wished property name in the reported violation, > Resteasy's conversion would take over from there. > > > 2013/9/19 Hardy Ferentschik <hardy(a)hibernate.org&gt; > > > > > On 19 Jan 2013, at 9:44 AM, Emmanuel Bernard <emmanuel(a)hibernate.org&gt; > > wrote: > > > > > It seems that what this user really needs is a way to convert the > > Set<ConstraintViolation> into another format entirely, JSON in this case. I > > wonder if we could find a more generic approach than just the ability to > > change properties names. > > > > Well, there are really two problems. First the creation of the JSON format > > and then the property name "conversion". I think they need to be addressed > > separately. Even if we had/offered something to convert the constraint > > violations, we still > > would report the actual property name. > > > > In the described use case I would write the conversion code myself. The > > constraint violation contains all the information needed to create the JSON > > format and do the name conversion. It should not be hard to write. > > > > --Hardy > > > > > > _______________________________________________ > > hibernate-dev mailing list > > hibernate-dev(a)lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hibernate-dev > > > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev