<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">That's a nice idea<div><br></div><div>class User {</div><div> @Duplicated</div><div> String password;</div><div><br></div><div> @Duplicated.Duplicate</div><div> String duplicatedPassword;</div><div>}</div><div><br></div><div>class {</div><div> @Causality</div><div> Date checkIn;</div><div><br></div><div> @Causality.After</div><div> Date checkout;</div><div>}</div><div><br></div><div>This exact model does not scale if several string or dates need to be compared and is weak on inheritance. A full scale qualifier model might be nice but it's one or two additional annotations to define per type.</div><div><br></div><div>Thoughts?</div><div><br></div><div><br><div><div>On 8 sept. 2011, at 22:15, Gerhard Petracek wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">as an alternative we could think about a solution >similar< to cdi qualifiers. that would be also useful for cross-field validation.<div>i would like to suggest a wiki which shows all possibilities side by side (+ examples).</div>
<div><br></div><div>regards,</div><div>gerhard</div><div><br>
<br></div><div><br><br><div class="gmail_quote">2011/9/8 Hardy Ferentschik <span dir="ltr"><<a href="mailto:hardy@hibernate.org">hardy@hibernate.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Wed, 07 Sep 2011 22:55:47 +0200, Sebastian Thomschke<br>
<<a href="mailto:sebastian.thomschke@web.de">sebastian.thomschke@web.de</a>> wrote:<br>
<br>
> Its a very unfortunate limitation in Java's reflection API that it does<br>
> not provide the ability to determine the declared parameter names. OVal<br>
> provides a pluggable parameter name resolver, with a very simple<br>
> interface:<br>
><br>
> public interface ParameterNameResolver<br>
> {<br>
> String[] getParameterNames(Constructor< ? > constructor) throws<br>
> ReflectionException;<br>
> String[] getParameterNames(Method method) throws<br>
> ReflectionException;<br>
> }<br>
<br>
</div>I like the idea of introducing an interface for parameter name resolution.<br>
The default and simple implementation would be the enumerated names.<br>
Other implementations could be based on byte code enhancing (like<br>
mentioned here)<br>
or a meta model created by an annotation processor (like Kevin suggested<br>
in HV-409).<br>
<font color="#888888"><br>
--Hardy<br>
</font><div><div></div><div class="h5"><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>
</div></div></blockquote></div><br></div>
_______________________________________________<br>beanvalidation-dev mailing list<br><a href="mailto:beanvalidation-dev@lists.jboss.org">beanvalidation-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/beanvalidation-dev<br></blockquote></div><br></div></body></html>