<br><div class="gmail_quote">On 26 October 2011 15:36, Emmanuel Bernard <span dir="ltr"><<a href="mailto:emmanuel@hibernate.org">emmanuel@hibernate.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word"><div><div class="im"><blockquote type="cite"><div><div class="gmail_quote"><div><br></div><div>IMHO, if the mechanism used to discover the ConstraintValidator implementations is pluggable, it should work.</div>
</div></div></blockquote><div><br></div></div><div>What do you have in mind? I don't mind having a pluggable discovery mechanism but we need a standard way for a constraint implementor to expose the fact that it implements validators for some constraints.</div>
</div></div></blockquote><div><br></div><div>I've nothing special in mind. By pluggable I mean a way to override the discovery mechanism like it's done with the ValidationProviderResolver. The way used to specify the ConstraintValidator implementations will remain the same. </div>
<div><br></div><div>Because I'm not sure it's possible to have a mechanism which works in a modular and non-modular world out of the box. For example, to make it work with OSGi you'll have to be depend on the API. AFAIK, JBoss Modules allows to import/export service resources.</div>
<div> </div><div>--Kevin</div></div>