Hey guys,

just heads up that what was discussed in this thread was just merged to wildfly-core
as part of https://github.com/wildfly/wildfly-core/pull/621

original "spec" is here https://gist.github.com/ctomc/91055a6f4e7502dcd130

There was also one additional improvement, that allows to use enhanced syntax also
on collection operation :map-* and :list-*

--
tomaz


On Mon, Aug 18, 2014 at 10:04 PM, Tomaž Cerar <tomaz.cerar@gmail.com> wrote:

On Mon, Aug 18, 2014 at 6:34 PM, Brian Stansberry <brian.stansberry@redhat.com> wrote:
3) DMR has a really simple interface -- 4 public classes, ModelNode,
ModelType, Property, ValueExpression. To be useful, ModelType.MAP will
require some sort of new concept, to express the type of the map value,
and perhaps the map key. So a 25% or more increase in the number of
types in the public API. Not a big deal by itself but it's a sign that
this isn't some minor change.


Maybe I wasn't clear enough what I meant here.
I only implied that we would add ModelType.MAP to jboss-dmr.

All other changes would be part of WildFly management,
with introducing new model key "key-type" and alike.

But I can see what you meant and I am leaning more and more on
*not* adding ModelType.MAP.

All we need can be handled as part of wildfly mgmt apis to hide as much
of "map internal impl" and as long people would use that api it wouldn't matter what impl is.
Once we move to annotation driven model most of this will be hidden anyway.