RFE: Consider using the swarm config-api for interaction with the wildfly DMR model

[heiko-braun]

IMO much of the hawkular-dmr-client [1] can be replaced by the swarm config-api [2].

[1] https://github.com/hawkular/hawkular-agent/tree/master/hawkular-dmr-client
[2] https://github.com/wildfly-swarm/wildfly-config-api

[jmazzitelli]

That makes four .. add it to the list :) We have this one developed in QE [3]
and there is a fourth out there somewhere, @ppalaga was looking at that one - its a compile-time code generator for DMR clients (perhaps that's this swarm config-api? I don't know if its the same one or a different one - so many now I can't keep them straight :) )

[3]https://github.com/Creaper-Project/creaper

[heiko-braun]

Right, it's what I've discussed with @ppalaga .

If I would have to make the choice then I would go with straight DMR. It's the most versatile approach.But I can understand that some people look for high level API that hides much of the DMR specifics.

The downside of using creaper is it's reliance on string parameters for keys and values of the model. In contrast to this the config-api is idomatic Java.

Furthermore both libraries have a slightly different value proposition. Creaper is geared towards testing purposes. The config-api on the otherhand aims at completeness and ease of use. I think the later is what @ppalaga was mostly interested in.