<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 18, 2014 at 6:34 PM, Brian Stansberry <span dir="ltr"><<a href="mailto:brian.stansberry@redhat.com" target="_blank">brian.stansberry@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":mk" class="a3s" style="overflow:hidden">3) DMR has a really simple interface -- 4 public classes, ModelNode,<br>
ModelType, Property, ValueExpression. To be useful, ModelType.MAP will<br>
require some sort of new concept, to express the type of the map value,<br>
and perhaps the map key. So a 25% or more increase in the number of<br>
types in the public API. Not a big deal by itself but it's a sign that<br>
this isn't some minor change.<br>
<div class=""></div></div></blockquote></div><br><br></div><div class="gmail_extra">Maybe I wasn't clear enough what I meant here. <br>I only implied that we would add ModelType.MAP to jboss-dmr.<br><br>All other changes would be part of WildFly management, <br>
with introducing new model key "key-type" and alike.<br><br></div><div class="gmail_extra">But I can see what you meant and I am leaning more and more on <br>*not* adding ModelType.MAP.<br><br></div><div class="gmail_extra">
All we need can be handled as part of wildfly mgmt apis to hide as much <br>of "map internal impl" and as long people would use that api it wouldn't matter what impl is.<br></div><div class="gmail_extra">Once we move to annotation driven model most of this will be hidden anyway.<br>
<br></div><div class="gmail_extra"><br></div></div>