anchor.diff:  management interface via a more strongly-typed API that sits above the DMR API. The
   https://github.com/hawkular/hawkular-agent/tree/master/hawkular-dmr-client/src/main/java/org/hawkular/dmrclient[DMR Client]
   provides this capability in a single-jar library. The Hawkular Monitor agent uses it, but since it is a
  -standalone library, anyone that wants to talk to WildFly's management interface can use it.
  +standalone library, anyone that wants to talk to WildFly's management interface can use it. Currently, its snapshots are
  +released on Nexus which you can
  +https://repository.jboss.org/nexus/content/repositories/snapshots/org/hawkular/agent/hawkular-dmr-client/[find here].
   
  -A simple example in its usage is as follows:
  +A simple example of its usage is as follows:
   [source,java]
   ----
   import org.jboss.as.controller.client.ModelControllerClient;
  
positive.code: 
  The Hawkular Monitor agent is a Wildfly subsystem extension deployed as a module inside Wildfly.
  At the time of writing, this currently works in Wildfly 8.2 Final.
  
  == How To Build
  . Clone https://github.com/hawkular/hawkular-agent[the source code]
  
negative.code: }
  ----
  
  You no longer have to worry about how to build DMR ModelNodes in the correct format to perform these kinds of operations.
  The Hawkular DMR Client API will build the ModelNode requests and process the ModelNode responses for you.
  
  CoreJBossASClient is one of several strongly-typed API objects that extend
  https://github.com/hawkular/hawkular-agent/blob/master/hawkular-dmr-client/src/main/java/org/hawkular/dmrclient/JBossASClient.java[JBossASClient].
  Others can be used to access common resource types in the DMR hierarchy, such as
  