<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Aug 15, 2013 at 9:48 AM, Galder Zamarreño <span dir="ltr"><<a href="mailto:galder@redhat.com" target="_blank">galder@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>
On Aug 14, 2013, at 11:14 PM, Ray Tsang <<a href="mailto:saturnism@gmail.com">saturnism@gmail.com</a>> wrote:<br>
<br>
> I actually did not enjoy writing parsers and config builders etc…<br>
<br></blockquote><div><br></div><div><div>i felt that writing the parsers are error prone - there are many places to touch when adding a property - maybe I just didn't follow the best example...</div><div><br></div><div>
i'm just thinking out loud but perhaps there is a way to consolidate the configuration builder, configuration, configuration parser, and xsd with a single set of metadata - after all, I think they are all trying to set the same set of properties.</div>
</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
^ Why not? Too verbose? Too many classes?<br>
<br>
I'd rather improve this than carry on supporting property-based configuration (any other type safety advocates?)<br></blockquote><div><br></div><div style>+1, the fact that I had to test both was a nuance...</div><div style>
<br></div><div style><br></div><div style><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Cheers,<br>
<div class=""><div class="h5"><br>
><br>
> On Aug 14, 2013, at 14:58, Mircea Markus <<a href="mailto:mmarkus@redhat.com">mmarkus@redhat.com</a>> wrote:<br>
><br>
>><br>
>> On 14 Aug 2013, at 18:48, Dennis Reed <<a href="mailto:dereed@redhat.com">dereed@redhat.com</a>> wrote:<br>
>><br>
>>>> I've written such parser on Friday, basically just copying and rewriting<br>
>>>> the SingleFileCacheStore stuff (adding my own properties instead). It<br>
>>>> took me about an hour and I don't hate anyone from infinispan team :)<br>
>>>> Maybe I am already advanced ISPN user, but I don't consider it as a<br>
>>>> complicated task as long as there is some template (simple cache-store<br>
>>>> implementation) I can use for reference.<br>
>>><br>
>>> If it took you an hour as an advanced user that's intimately familiar<br>
>>> with Infinispan to implement it and get it working,<br>
>>> that means for many of our customers it could take days, and quite a few<br>
>>> interactions with support.<br>
>>><br>
>>> Compare that to the current implementation where ISPN does the XML<br>
>>> parsing and calls setters, which takes 0 time no matter the competence<br>
>>> of the user.<br>
>>><br>
>>> I'm 100% *against* forcing customers to write their own XML parsing.<br>
>><br>
>> +1<br>
>> The current parsing-free approach will be kept. Just that we'll add a template for writing stores that would contain a sample optional parser.<br>
>><br>
>> Cheers,<br>
>> --<br>
>> Mircea Markus<br>
>> Infinispan lead (<a href="http://www.infinispan.org" target="_blank">www.infinispan.org</a>)<br>
>><br>
>><br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> infinispan-dev mailing list<br>
>> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
> _______________________________________________<br>
> infinispan-dev mailing list<br>
> <a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
<br>
<br>
</div></div><div class="im">--<br>
Galder Zamarreño<br>
<a href="mailto:galder@redhat.com">galder@redhat.com</a><br>
<a href="http://twitter.com/galderz" target="_blank">twitter.com/galderz</a><br>
<br>
Project Lead, Escalante<br>
<a href="http://escalante.io" target="_blank">http://escalante.io</a><br>
<br>
Engineer, Infinispan<br>
<a href="http://infinispan.org" target="_blank">http://infinispan.org</a><br>
<br>
<br>
</div><div class=""><div class="h5">_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
</div></div></blockquote></div><br></div></div>