<p>Hi Matt,</p>
<p>You can find the discussion around the original proposal back from February at <br>
<a href="http://lists.jboss.org/pipermail/beanvalidation-dev/2012-February/000248.html">http://lists.jboss.org/pipermail/beanvalidation-dev/2012-February/000248.html</a> </p>
<p>--Gunnar</p>
<div class="gmail_quote">Am 12.06.2012 23:53 schrieb "Matt Benson" <<a href="mailto:mbenson@apache.org">mbenson@apache.org</a>>:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Can someone point me to the initial discussion around the original<br>
ConfigurationSource changes? I have some concerns but I'd like to be<br>
able to study up to be sure I understand the decisions that were made<br>
(despite this thread's implying that the changes aren't set in stone).<br>
<br>
Thanks,<br>
Matt<br>
<br>
On Tue, Jun 12, 2012 at 3:50 PM, Gunnar Morling <<a href="mailto:gunnar@hibernate.org">gunnar@hibernate.org</a>> wrote:<br>
> Any preferences or other suggestions?<br>
><br>
> --Gunnar<br>
><br>
><br>
> 2012/6/2 Gunnar Morling <<a href="mailto:gunnar@hibernate.org">gunnar@hibernate.org</a>>:<br>
>> 2012/6/1 Emmanuel Bernard <<a href="mailto:emmanuel@hibernate.org">emmanuel@hibernate.org</a>>:<br>
>>><br>
>>> We can also imagine a specific provider offering an alternative source of configuration and using this interface to expose it.<br>
>>> That was the rational behind the use of "typically".<br>
>><br>
>> Maybe some bits of explantation would make it clearer?<br>
>><br>
>> "Return information retrieved from the user-provided default<br>
>> configuration. While loaded from the <i>META-INF/validation.xml</i><br>
>> file by default, implementations are free to provide other means of<br>
>> default configuration such as a properties file."<br>
>><br>
>>>> * What do I return if there is no validation.xml? null? Or the class names of the implementations default implementations?<br>
>>><br>
>>> Good question, I'm in favor of null. anyone against that?<br>
>><br>
>> +1 for returning null.<br>
>><br>
>>><br>
>>>><br>
>>>> * Last but not least, why ConfigurationSource?<br>
>>> Technically this is the configuration but we already have a programmatic Configuration object.<br>
>>><br>
>>> Ideas?<br>
>>><br>
>>> - XmlConfiguration<br>
>>> - StaticConfiguration<br>
>>> - ConfigurationSource<br>
>>> - ConfigurationParameters<br>
>>> - ?<br>
>><br>
>> Some more ideas:<br>
>><br>
>> - DefaultConfiguration<br>
>> - UserDefaultConfiguration<br>
>> - ExternalConfiguration<br>
>> - BootstrapConfiguration<br>
>><br>
>> I find the term "source" a bit mis-leading, as I would regard<br>
>> something like "XML" or "properties file" as source, but the returned<br>
>> object from that source as "configuration". I think I'm preferring<br>
>> (User)DefaultConfiguration, as it IMO clearly describes the object's<br>
>> intention.<br>
>><br>
>> I've created BVAL-293 [1] for any clarifications/refinements around<br>
>> ConfigurationSource.<br>
>><br>
>> --Gunnar<br>
>><br>
>> [1] <a href="https://hibernate.onjira.com/browse/BVAL-293" target="_blank">https://hibernate.onjira.com/browse/BVAL-293</a><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>
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>
</blockquote></div>