[hibernate-dev] [HV] Extending ParameterNameProvider contract for other element types

Gunnar Morling gunnar at hibernate.org
Thu Sep 19 04:30:07 EDT 2013


Yes, the use case seems quite specific. I've created
https://hibernate.atlassian.net/browse/HV-823 to keep track of this.


2013/9/19 Hardy Ferentschik <hardy at hibernate.org>

> 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 at hibernate.org> 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-jackson-using-the-jsonproperty-value-as-the-constraint
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
>


More information about the hibernate-dev mailing list