Re: [bv-dev] Should we expose group conversions via meta-data API?
Hi all,
I think one natural way for representing group conversions in the metadata
API would be to add a method
Map<Class<?>, Class<?>> getGroupConversions()
to ParameterDescriptor, ReturnValueDescriptor and PropertyDescriptor
(that's also how conversions are represented internally in the RI).
Any thoughts on that, or other suggestions? If no one objects, I'd move
forward and add the method to the spec and API.
--Gunnar
2013/1/18 Gunnar Morling <gunnar(a)hibernate.org>
> We should.
Ok, I've created https://hibernate.onjira.com/browse/BVAL-361 for this.
--Gunnar
2013/1/18 Emmanuel Bernard <emmanuel(a)hibernate.org>
> We should.
>
> The reason the metadata API is complete is so that non Java system can
> propagate the constraints and logic of validation. Client side presentation
> framework was the canonical example.
>
> On 17 janv. 2013, at 21:44, Gunnar Morling <gunnar(a)hibernate.org> wrote:
>
> > Hi all,
> >
> > As the title says: should we provide a way to access configured group
> conversions via the meta-data API?
> >
> > I'm undecided, I don't really see where this would be useful, OTOH
> we've exposed all BV-related configurations via the meta-data API so far,
> so I guess we probably should for the sake of completeness.
> >
> > Thoughts?
> >
> > --Gunnar
> >
> > _______________________________________________
> > beanvalidation-dev mailing list
> > beanvalidation-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
>
> _______________________________________________
> beanvalidation-dev mailing list
> beanvalidation-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/beanvalidation-dev
>
Attachments:
- attachment.html (text/html — 3.2 KB)