anchor.diff:  [standalone@localhost:9990 /] /socket-binding-group=standard-sockets/socket-binding=http:write-attribute(name=port,value=8080)
   ----
   
  -==== GUI
  +==== (NOT COVERING) GUI
   
   CLI can be started with a GUI instead of a command line. It allows you to browse through different nodes and commands and operations supported on a node. Commands are automatically created and can be submitted to the server. Applications can be deployed and undeployed as well.
   
  
positive.code: 
  === OpenShift
  
  . Create an OpenShift application using WildFly cartridge
  . Access the WildFly administration console using port forwarding
  . Import the created application in JBoss Developer Studio/IntelliJ
  . Make changes to the application and view them in the deployed application
  . Add a simple Java EE 7 component to the application
  
  === Cloudbees
negative.code: +
  The prompt indicates that `jboss-cli' is connected to a standalone instance on port `19990'.
  
  WildFly internal management model consists of _management resources_ that are added, removed, or modified by using _operations_ and _commands_. Operations are low level but a comprehensive way to manage the server. Commands are more user-friendly, although most of them still translate into operation requests and some of them even into a few composite operation requests.
  
  All resources are organized in a tree. The path to the node in the tree for a particular resource is its _address_ and is identified by `/`.
  
  