<div dir="ltr">Ok, then<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div> <span style="font-family:arial,sans-serif;font-size:13px">Set<GroupConversionDescriptor> </span><span style="font-family:arial,sans-serif;font-size:13px">getGroupConversions()</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">it is.</span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div><div style><span style="font-family:arial,sans-serif;font-size:13px">Thanks,</span></div><div style><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div style><span style="font-family:arial,sans-serif;font-size:13px">--Gunnar</span></div>
<div style><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/1/31 Emmanuel Bernard <span dir="ltr"><<a href="mailto:emmanuel@hibernate.org" target="_blank">emmanuel@hibernate.org</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm not sure. I think the annotation EG consider it bad practice and<br>
implementation detail abouse to use the annotations as glorified interfaces.<br>
<br>
In your case that's ok-ish (minor the XML DD) but if we want to add<br>
behavior later on we might be stuck.<br>
<div class="HOEnZb"><div class="h5"><br>
On Thu 2013-01-31 13:43, Gunnar Morling wrote:<br>
> Yeah, that's a good point of course. I liked using a map as it very<br>
> naturally expressed that there may be only one rule per "from" type, but<br>
> making the API evolvable is more important I guess.<br>
><br>
> How about using ConvertGroup directly, i.e. return a Set<ConvertGroup>? In<br>
> that context the name doesn't read that well, but OTOH<br>
> GroupConvertionDescriptor<br>
> would more or less resemble ConvertGroup. WDYT?<br>
><br>
><br>
> 2013/1/31 Emmanuel Bernard <<a href="mailto:emmanuel@hibernate.org">emmanuel@hibernate.org</a>><br>
><br>
> > I'd rather have a GroupConversionDescriptor representing the from / to.<br>
> > My reason is that if we add a new attribute to @ConvertGroup later, we<br>
> > will be able to add it on the descriptor as well.<br>
> ><br>
> > I think we tend to use a Set for the collection of elements in the spec.<br>
> ><br>
> > So that would become a Set<GroupConvertionDescriptor>.<br>
> ><br>
> > Emmanuel<br>
> ><br>
> > On Wed 2013-01-30 22:39, Gunnar Morling wrote:<br>
> > > Hi all,<br>
> > ><br>
> > > I think one natural way for representing group conversions in the<br>
> > metadata<br>
> > > API would be to add a method<br>
> > ><br>
> > > Map<Class<?>, Class<?>> getGroupConversions()<br>
> > ><br>
> > > to ParameterDescriptor, ReturnValueDescriptor and PropertyDescriptor<br>
> > > (that's also how conversions are represented internally in the RI).<br>
> > ><br>
> > > Any thoughts on that, or other suggestions? If no one objects, I'd move<br>
> > > forward and add the method to the spec and API.<br>
> > ><br>
> > > --Gunnar<br>
> > ><br>
> > ><br>
> > ><br>
> > > 2013/1/18 Gunnar Morling <<a href="mailto:gunnar@hibernate.org">gunnar@hibernate.org</a>><br>
> > ><br>
> > > > > We should.<br>
> > > ><br>
> > > > Ok, I've created <a href="https://hibernate.onjira.com/browse/BVAL-361" target="_blank">https://hibernate.onjira.com/browse/BVAL-361</a> for<br>
> > this.<br>
> > > ><br>
> > > > --Gunnar<br>
> > > ><br>
> > > ><br>
> > > > 2013/1/18 Emmanuel Bernard <<a href="mailto:emmanuel@hibernate.org">emmanuel@hibernate.org</a>><br>
> > > ><br>
> > > >> We should.<br>
> > > >><br>
> > > >> The reason the metadata API is complete is so that non Java system can<br>
> > > >> propagate the constraints and logic of validation. Client side<br>
> > presentation<br>
> > > >> framework was the canonical example.<br>
> > > >><br>
> > > >> On 17 janv. 2013, at 21:44, Gunnar Morling <<a href="mailto:gunnar@hibernate.org">gunnar@hibernate.org</a>><br>
> > wrote:<br>
> > > >><br>
> > > >> > Hi all,<br>
> > > >> ><br>
> > > >> > As the title says: should we provide a way to access configured<br>
> > group<br>
> > > >> conversions via the meta-data API?<br>
> > > >> ><br>
> > > >> > I'm undecided, I don't really see where this would be useful, OTOH<br>
> > > >> we've exposed all BV-related configurations via the meta-data API so<br>
> > far,<br>
> > > >> so I guess we probably should for the sake of completeness.<br>
> > > >> ><br>
> > > >> > Thoughts?<br>
> > > >> ><br>
> > > >> > --Gunnar<br>
> > > >> ><br>
> > > >> > _______________________________________________<br>
> > > >> > beanvalidation-dev mailing list<br>
> > > >> > <a href="mailto:beanvalidation-dev@lists.jboss.org">beanvalidation-dev@lists.jboss.org</a><br>
> > > >> > <a href="https://lists.jboss.org/mailman/listinfo/beanvalidation-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/beanvalidation-dev</a><br>
> > > >><br>
> > > >> _______________________________________________<br>
> > > >> beanvalidation-dev mailing list<br>
> > > >> <a href="mailto:beanvalidation-dev@lists.jboss.org">beanvalidation-dev@lists.jboss.org</a><br>
> > > >> <a href="https://lists.jboss.org/mailman/listinfo/beanvalidation-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/beanvalidation-dev</a><br>
> > > >><br>
> > > ><br>
> > > ><br>
> ><br>
> > > _______________________________________________<br>
> > > beanvalidation-dev mailing list<br>
> > > <a href="mailto:beanvalidation-dev@lists.jboss.org">beanvalidation-dev@lists.jboss.org</a><br>
> > > <a href="https://lists.jboss.org/mailman/listinfo/beanvalidation-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/beanvalidation-dev</a><br>
> ><br>
> > _______________________________________________<br>
> > beanvalidation-dev mailing list<br>
> > <a href="mailto:beanvalidation-dev@lists.jboss.org">beanvalidation-dev@lists.jboss.org</a><br>
> > <a href="https://lists.jboss.org/mailman/listinfo/beanvalidation-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/beanvalidation-dev</a><br>
> ><br>
<br>
> _______________________________________________<br>
> beanvalidation-dev mailing list<br>
> <a href="mailto:beanvalidation-dev@lists.jboss.org">beanvalidation-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/beanvalidation-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/beanvalidation-dev</a><br>
<br>
_______________________________________________<br>
beanvalidation-dev mailing list<br>
<a href="mailto:beanvalidation-dev@lists.jboss.org">beanvalidation-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/beanvalidation-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/beanvalidation-dev</a><br>
</div></div></blockquote></div><br></div>