hi,<div><br></div><div>i was going to suggest something similar.</div><div><br></div><div>we could provide a simple adapter interface with a method like:</div><div><T> T resolveBean(Class<T> targetType)</div><div>
(and if we would like to support dependent beans, we should think about an additional dispose method.)</div><div><br></div><div>the only restriction is the manual usage of methods like ValidatorContext#messageInterpolator.</div>
<div>however, since it would be possible to configure those parts via a dependency injection container like cdi, it isn't a big issue.</div><div><br></div><div>regards,</div><div>gerhard</div><div><br></div><div><br>
</div>
<div><br><div class="gmail_quote">2012/1/3 Michael Nascimento <span dir="ltr"><<a href="mailto:misterm@gmail.com">misterm@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p>What about a different proposal: looking up the interface implementation using ServiceLoader? Then there would be nothing special about it.</p>
<p>Regards,<br>
Michael</p>
<div class="gmail_quote">On 3 Jan 2012 17:25, "Emmanuel Bernard" <<a href="mailto:emmanuel@hibernate.org" target="_blank">emmanuel@hibernate.org</a>> wrote:<br type="attribution"></div>
<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></blockquote></div><br></div>