rboss 0.9.1 → 0.9.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 5c865678a219fd236a68663a11b06292b39d1d30
-  data.tar.gz: ea7e7538b6bcb61c42cee3edaf3618a85df8d9d8
+  metadata.gz: 1e20ec4987337d606798b75b915e2b222598d025
+  data.tar.gz: de04752a875590d1fa5c4819988bd6bed4b08bbf
 SHA512:
-  metadata.gz: fe288a4166e76bf5c80b41ce303fde89966e8c36c5d8d486c97b416f4317b848c6cb7921ae9f1e40ca063ebe340e1431abd30e329985a421745a383105ce8b2c
-  data.tar.gz: 91cf9958af7217a830017acaed421c4913d1f5872355b30380ff216144564210d6e194530a91198df042293c6305b1527f573c55c24281c54c8c80249e361c02
+  metadata.gz: 709cd9e696f2963a3e59798c22666d175c11f8fac7b429bd2ee87aa591f0ccad35e87beced870b82f0640818f05b273cede7a0a0a9c97b64382a9d3c06cee0c4
+  data.tar.gz: df7b4d13cf2787d7a01ed1258ee422739de9f1d6aa39ec76d25b742a0f59d18e04fdca9c636450a9c4dbdce91c7352e5af1c4f8d23eb826989f6c6fee36cab3b

data/.idea/encodings.xml

@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project version="4">
+  <component name="Encoding" useUTFGuessing="true" native2AsciiForPropertiesFiles="false" />
+</project>
+

data/.idea/misc.xml

@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project version="4">
+  <component name="IdProvider" IDEtalkID="1EEE3103C92A9F3F24A791D6B22E1653" />
+  <component name="ProjectRootManager" version="2" languageLevel="JDK_1_6" assert-keyword="true" jdk-15="true" project-jdk-name="RVM: ruby-2.1.2" project-jdk-type="RUBY_SDK" />
+</project>

data/.idea/modules.xml

@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project version="4">
+  <component name="ProjectModuleManager">
+    <modules>
+      <module fileurl="file://$PROJECT_DIR$/.idea/rboss.iml" filepath="$PROJECT_DIR$/.idea/rboss.iml" />
+    </modules>
+  </component>
+</project>
+

data/.idea/rboss.iml

@@ -0,0 +1,65 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<module type="RUBY_MODULE" version="4">
+  <component name="FacetManager">
+    <facet type="gem" name="Ruby Gem">
+      <configuration>
+        <option name="GEM_APP_ROOT_PATH" value="$MODULE_DIR$" />
+        <option name="GEM_APP_TEST_PATH" value="" />
+        <option name="GEM_APP_LIB_PATH" value="$MODULE_DIR$/lib" />
+      </configuration>
+    </facet>
+  </component>
+  <component name="ModuleRunConfigurationManager">
+    <configuration default="false" name="Public Interface" type="RubyRunConfigurationType" factoryName="Ruby">
+      <module name="rboss" />
+      <RUBY_RUN_CONFIG NAME="RUBY_ARGS" VALUE="-e $stdout.sync=true;$stderr.sync=true;load($0=ARGV.shift)" />
+      <RUBY_RUN_CONFIG NAME="WORK DIR" VALUE="$MODULE_DIR$/bin" />
+      <RUBY_RUN_CONFIG NAME="SHOULD_USE_SDK" VALUE="false" />
+      <RUBY_RUN_CONFIG NAME="ALTERN_SDK_NAME" VALUE="" />
+      <RUBY_RUN_CONFIG NAME="myPassParentEnvs" VALUE="true" />
+      <envs />
+      <EXTENSION ID="BundlerRunConfigurationExtension" bundleExecEnabled="true" />
+      <EXTENSION ID="JRubyRunConfigurationExtension" NailgunExecEnabled="false" />
+      <EXTENSION ID="RubyCoverageRunConfigurationExtension" enabled="false" sample_coverage="true" track_test_folders="true" runner="rcov">
+        <COVERAGE_PATTERN ENABLED="true">
+          <PATTERN REGEXPS="/.rvm/" INCLUDED="false" />
+        </COVERAGE_PATTERN>
+      </EXTENSION>
+      <EXTENSION ID="org.jetbrains.plugins.ruby.motion.run.MotionSimulatorRunExtension" />
+      <RUBY_RUN_CONFIG NAME="SCRIPT_PATH" VALUE="$MODULE_DIR$/bin/rboss-cli" />
+      <RUBY_RUN_CONFIG NAME="SCRIPT_ARGS" VALUE="--interface public" />
+      <RunnerSettings RunnerId="RubyRunner" />
+      <ConfigurationWrapper RunnerId="RubyRunner" />
+      <method />
+    </configuration>
+    <configuration default="false" name="IRB console: rboss" type="IrbRunConfigurationType" factoryName="IRB console" temporary="true">
+      <module name="rboss" />
+      <IRB_RUN_CONFIG NAME="RUBY_ARGS" VALUE="-e $stdout.sync=true;$stderr.sync=true;load($0=ARGV.shift)" />
+      <IRB_RUN_CONFIG NAME="WORK DIR" VALUE="$MODULE_DIR$" />
+      <IRB_RUN_CONFIG NAME="SHOULD_USE_SDK" VALUE="false" />
+      <IRB_RUN_CONFIG NAME="ALTERN_SDK_NAME" VALUE="" />
+      <IRB_RUN_CONFIG NAME="myPassParentEnvs" VALUE="true" />
+      <envs />
+      <EXTENSION ID="BundlerRunConfigurationExtension" bundleExecEnabled="false" />
+      <EXTENSION ID="JRubyRunConfigurationExtension" NailgunExecEnabled="false" />
+      <EXTENSION ID="RubyCoverageRunConfigurationExtension" enabled="false" sample_coverage="true" track_test_folders="true" runner="rcov">
+        <COVERAGE_PATTERN ENABLED="true">
+          <PATTERN REGEXPS="/.rvm/" INCLUDED="false" />
+        </COVERAGE_PATTERN>
+      </EXTENSION>
+      <EXTENSION ID="org.jetbrains.plugins.ruby.motion.run.MotionSimulatorRunExtension" />
+      <IRB_RUN_CONFIG NAME="SCRIPT_PATH" VALUE="$USER_HOME$/.rvm/rubies/ruby-2.1.2/bin/irb" />
+      <IRB_RUN_CONFIG NAME="SCRIPT_ARGS" VALUE="--prompt simple" />
+      <IRB_RUN_CONFIG NAME="IS_RAILS_CONSOLE" VALUE="false" />
+      <RunnerSettings RunnerId="RubyRunner" />
+      <ConfigurationWrapper RunnerId="RubyRunner" />
+      <method />
+    </configuration>
+  </component>
+  <component name="NewModuleRootManager" inherit-compiler-output="false">
+    <content url="file://$MODULE_DIR$" />
+    <orderEntry type="inheritedJdk" />
+    <orderEntry type="sourceFolder" forTests="false" />
+    <orderEntry type="library" scope="PROVIDED" name="bundler (v1.7.2, RVM: ruby-2.1.2) [gem]" level="application" />
+  </component>
+</module>

data/.idea/scopes/scope_settings.xml

@@ -0,0 +1,5 @@
+<component name="DependencyValidationManager">
+  <state>
+    <option name="SKIP_IMPORT_STATEMENTS" value="false" />
+  </state>
+</component>

data/.idea/vcs.xml

@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project version="4">
+  <component name="VcsDirectoryMappings">
+    <mapping directory="$PROJECT_DIR$" vcs="Git" />
+  </component>
+</project>
+

data/Gemfile

@@ -1,5 +1,5 @@
-source "http://rubygems.org"
+source 'http://rubygems.org'
 
 gemspec
 
-gem 'yummi'
+gem 'yummi', '~> 0.9.3'

data/README.md

@@ -1,30 +1,21 @@
 rboss
 =============
 
-Use this tool to create profiles for JBoss Application Server and use twiddle to scan
-a running JBoss AS or execute scripts.
-
+This tool helps you manage a JBoss application server (EAP or Wildfly) by encapsulating `jboss-cli` in a usefull and customizable command line tool.
 
 Installation
 -----------
 
     gem install rboss
 
-### Direct Dependencies
-
-    * yummi
-
 ### Configuration
 
-Set a RBOSS_CLI_HOME variable pointing to your JBoss AS home location that has jboss-cli
-for using rboss-cli, for using twiddle, set a RBOSS_TWIDDLE_HOME variable pointing to you JBoss AS 
-that has twiddle.
+Set a `RBOSS_CLI_HOME` variable pointing to your JBoss AS home location that has `jboss-cli` for using `rboss-cli`.
 
 Using rboss-cli
 -----------
 
-rboss-cli is a helper tool for jboss-cli, it maps resource paths and helps the operation
-invoke.
+`rboss-cli` is a helper tool for `jboss-cli`, it maps resource paths and helps the operation invoke.
 
 ### Basics
 
@@ -40,22 +31,20 @@ You can scan resources, detail information and execute operations.
 
 ### Invoking Operations
 
-To see the operations for a resource, use the "--list-operations" or "-l" option:
+To see the operations for a resource, use the `--list-operations` or `-l` option:
 
     rboss-cli --server --list-operations
 
-To detail an operation, use the "--detail-operation" or "-d" option:
+To detail an operation, use the `--detail-operation` or `-d` option:
 
     rboss-cli --server --detail-operation shutdown
 
-This will print a table showing both request and response parameters. To invoke the
-operation, use the "--operation" or "-o" option:
+This will print a table showing both request and response parameters. To invoke the operation, use the `--operation` or `-o` option:
 
     rboss-cli --server --operation shutdown
     rboss-cli --server -o shutdown
 
-Since this operation requires a parameter, rboss-cli will ask you to input them. If you
-want to pass the required parameters, use the "--arguments" or "-a" option:
+Since this operation requires a parameter, rboss-cli will ask you to input them. If you want to pass the required parameters, use the `--arguments` or `-a` option:
 
     rboss-cli --server --operation shutdown --arguments restart=true
     rboss-cli --server -o shutdown -a restart=true
@@ -64,42 +53,41 @@ Multiple arguments are supported using commas:
 
     rboss-cli --some-resource -o operation -a arg1=value1,arg2=value
 
-If you want to skip optional arguments, use the "--skip-optional". rboss-cli will not ask
-you to input the arguments, leaving "--arguments" as the only way to set them.
+If you want to skip optional arguments, use the `--skip-optional`. `rboss-cli` will not ask you to input optional arguments, leaving `--arguments` as the only way to set them.
 
-See rboss-cli --help for a complete list of commands.
+See `rboss-cli --help` for a complete list of commands.
 
-### Known Issues
+### Bash Completion
 
-The datasource mapping (--datasource) retrieves incorrect information if you call either
-detail operation or invoke operation for the operation add. This is caused because the
-command '/subsystem=datasources/data-source=:read-operation-description(name=add)' needs
-to be executed as
-'/subsystem=datasources/data-source=ANY_VALUE:read-operation-description(name=add)',
-leaving the '--datasource any' as a workaround.
+You can also source the `rboss-cli-bash-completion` file to make use of the completion for the `rboss-cli`. The completion works for parameters, resource arguments and operations.
 
-    rboss-cli --datasource --detail-operation add
-    rboss-cli --datasource a --detail-operation add
+    $ rboss-cli --dat[TAB]
+    $ rboss-cli --datasource Exa[TAB]
+    $ rboss-cli --datasource ExampleDS
 
-### Configuring CLI mappings
+Keep in mind that if you need completion for a different server than `local` (the default server), you should start the command with `--connect` or `-c`:
 
-To create and override mappings, just put a yaml file in "~/.rboss/rboss-cli/resources". The filename will
-be used to identify the operation. Example: placing a file named datasource.yaml will override the
---datasource option and a file named logger.yaml will create a new option (--logger).
+    $ rboss-cli --connect my[TAB]
+    $ rboss-cli --connect myserver
+    $ rboss-cli --connect myserver --dat[TAB]
+    $ rboss-cli --connect myserver --datasource Exa[TAB]
+    $ rboss-cli --connect myserver --datasource ExampleDS
 
-The yaml must contain the given definitions:
+### Configuring CLI mappings
+
+To create and override mappings, just put a yaml file in `~/.rboss/rboss-cli/resources`. The filename will be used to identify the operation. Example: placing a file named datasource.yaml will override the `--datasource` option and a file named `logger.yaml` will create a new option (`--logger`). The yaml must contain the given definitions:
 
-* description: an explaining text to appear in command usage (--help)
-* path: the path to invoke the operations, may take a ${NAME} if the path contains a resource name
+* description: an explaining text to appear in command usage (`--help`)
+* path: the path to invoke the operations, may take a `${NAME}` if the path contains a resource name
 * scan (optional): a command to scan resources (by using this, the option may take an array of resource names)
-* print (optional): an array of table definitions to print with "read-resource" operation.
+* print (optional): an array of table definitions to print with `read-resource` operation.
 
 Examples:
 
     ---
     description: Datasource Information
-    path: /subsystem=datasources/data-source=${NAME}
-    scan: ls /subsystem=datasources/data-source    
+    path: ${DOMAIN_HOST}${DOMAIN_SERVER}/subsystem=datasources/data-source=${NAME}
+    scan: ls ${DOMAIN_HOST}${DOMAIN_SERVER}/subsystem=datasources/data-source
     print:
       - id: config
         title: Datasource Details
@@ -165,7 +153,7 @@ Examples:
 
     ---
     description: Detail Server Information
-    path: /core-service=
+    path: ${DOMAIN_HOST}${DOMAIN_SERVER}/core-service=
     print:
     - id: platform
       title: Operating System Information
@@ -208,7 +196,7 @@ To configure a table to print, just use the following parameters:
 All mappings (formatter, colorizer and health checker) should be mapped using the following conventions:
 
 * the key should be the property name (replace '-' with '_')
-* the value should be the message to send to RBoss::Formatters, RBoss::HealthCheckers or RBoss::Colorizers
+* the value should be the message to send to `RBoss::Formatters`, `RBoss::HealthCheckers` or `RBoss::Colorizers`
 * if the message takes parameters, they must be specified in a form of a hash after the message
 
 Examples:
@@ -239,7 +227,7 @@ Examples:
 
 ### Adding new components
 
-To add new Colorizers, Formatters or HealthCheckers, just put the code in the "~/.rboss/rboss.rb" file.
+To add new `Colorizers`, `Formatters` or `HealthCheckers`, just put the code in the `~/.rboss/rboss.rb` file.
 
 Example:
 
@@ -258,357 +246,6 @@ From now you can use this colorizer
 
 The components included are defined in the following files:
 
-* /lib/rboss/view/colorizers.rb
-* /lib/rboss/view/formatters.rb
-* /lib/rboss/view/health_checkers.rb
-
-Using rboss-twiddle
------------
-
-### Basics
-
-Simply do a "cd" to your JBoss Home and use it
-
-    rboss-twiddle --help
-
-You can scan resources like: datasources, queues, connectors, webapps, ...
-
-    rboss-twiddle --datasource --webapp
-    rboss-twiddle --all
-
-If you don't need to scan for resources, you can specify them for monitoring:
-
-    rboss-twiddle --webapp jmx-console,admin-console
-
-Combine with "watch" to get a simple and instantly monitoring:
-
-    watch --interval=1 rboss-twiddle --webapp jmx-console,admin-console
-
-Retrieve property values with --get:
-
-    rboss-twiddle --get webapp:jmx-console,maxSessions
-    rboss-twiddle --get server-info,FreeMemory
-
-Set values with --set:
-
-    rboss-twiddle --set connector:http-127.0.0.1-8080,maxThreads,350
-
-Execute commands with --invoke:
-
-    rboss-twiddle --invoke server,shutdown
-    rboss-twiddle --invoke web-deployment:jmx-console,stop
-
-Extending mbeans
-
-You can use a file in ~/.rboss/twiddle.rb for mapping new mbeans or overriding the defaults
-
-    RBoss::Twiddle::Monitor.defaults[:http_request] = {
-      :description => 'Request for http protocol',
-      :pattern => 'jboss.web:type=GlobalRequestProcessor,name=http-127.0.0.1-8080',
-      :properties => %W(requestCount errorCount maxTime)
-    }
-
-And use it normally
-
-    rboss-twiddle --http-request
-
-You can do every action using custom mbeans
-
-    rboss-twiddle --invoke http-request,resetCounters
-
-Configurations can be saved using --save
-
-    rboss-twiddle --save jon --port 2099
-
-And used with -c or --config
-
-    rboss-twiddle -c jon --server-config
-
-### Customizing MBeans
-
-Every time you run the rboss-twiddle command, this gem will load the ~/.rboss/rboss.rb file,
-which can be used to customize the mbeans.
-
-    defaults = RBoss::Twiddle::Monitor.defaults
-    defaults[:logger] = {
-      :description => 'Logger Service',
-      :pattern => 'jboss.system:service=Logging,type=Logger'
-    }
-
-This will add a custom mbean whose identifier is 'logger'. From that, you can use therboss-
-twiddle command on it.
-
-    rboss-twiddle --invoke logger debug,message
-
-If your mbean name depends on a resource name (like the connector mbean), you can use
-a '#{resource}' string to pass the resource in the command line.
-
-    defaults[:mymbean] => {
-      :description => 'My Custom MBean',
-      :pattern => 'jboss.custom:type=CustomMBean,name=#{resource}'
-    }
-
-Don't forget to use single quotes on that. The rboss-twiddle command will be:
-
-    rboss-twiddle --get mymbean:Name,MBeanProperty
-
-If this mbean is scannable, you can use a :scan key:
-
-    defaults[:mymbean] => {
-      :description => 'My Custom MBean',
-      :pattern => 'jboss.custom:type=CustomMBean,name=#{resource}',
-      :scan => proc do
-        # queries and pass each result do the block
-        query "jboss.custom:type=CustomMBean,*" do |path|
-          path.gsub "jboss.custom:type=CustomMBean,name=", ""
-        end
-      end
-    }
-
-Now you can scan for resources of your custom MBean by using:
-
-    rboss-twiddle --mymbean
-
-If your MBean has some properties that should appear in a table for instant monitoring,
-just add a :properties key:
-
-    defaults[:mymbean] => {
-      :description => 'My Custom MBean',
-      :pattern => 'jboss.custom:type=CustomMBean,name=#{resource}',
-      :properties => %W(activeCount currentFree maxAvailable),
-      :header => ['Active Count', 'Current Free', 'Max Available'],
-      :scan => proc do
-        # queries and pass each result do the block
-        query "jboss.custom:type=CustomMBean,*" do |path|
-          path.gsub "jboss.custom:type=CustomMBean,name=", ""
-        end
-      end
-    }
-
-If this MBean maps a component that can be monitored for health state, you can map the
-limits by using a :health key:
-
-    defaults[:mymbean] => {
-      :description => 'My Custom MBean',
-      :pattern => 'jboss.custom:type=CustomMBean,name=#{resource}',
-      :properties => %W(activeCount currentFree maxAvailable),
-      :header => ['Active Count', 'Current Free', 'Max Available'],
-      :health => {
-        :active_count => {
-          :percentage => { # uses a percentage based check
-            :max => :max_available,
-            :using => :active_count #or use :free if you have the number of free resources
-          }
-        }
-      },
-      :scan => proc do
-        # queries and pass each result do the block
-        query "jboss.custom:type=CustomMBean,*" do |path|
-          path.gsub "jboss.custom:type=CustomMBean,name=", ""
-        end
-      end
-    }
-
-Customizing health, formatters and colors are the same as customizing in rboss-cli. You can
-use the indexes of the values (in that case, 2 for :max and 0 for :using) or the header values
-in downcase and underscores.
-
-Using rboss-profile
------------
-
-### Basics
-
-Simply do a "cd" to your JBoss Home and use it
-
-    rboss-profile --help
-
-All configuration can be stored in a single yaml file containing an array of components
-and its configuration:
-
-    - deploy_folder: deploy/datasources
-    - deploy_folder: deploy/apps
-    - jmx
-    - run_conf:
-        :heap_size: 1024m
-        :perm_size: 512m
-        :debug: :socket
-
-You can specify any command-line arguments directly in yaml file:
-
-    - :params:
-        :jboss_home: /home/user/jboss/org/jboss-5
-        :type: org
-        :version: 5.1
-        :base_profile: all
-        :profile: my_profile
-
-### Configuring deploy folders
-
-Use "deploy_folder" component and the desired folder. If the folder starts with a "/" or
-doesn't start with "deploy", the entries in VFS will be added.
-
-    # Will be in $JBOSS_HOME/server/$PROFILE/deploy/application
-    - deploy_folder: deploy/applications
-    # Will be in $JBOSS_HOME/server/$PROFILE/custom/application
-    - deploy_folder: custom/applications
-    - deploy_folder: /opt/deploy
-
-### Configuring jmx
-
-Use "jmx" component:
-
-    # user and password are "admin" by default
-    - jmx
-    - jmx:
-        :user: admin
-        :password: admin
-
-Basically, this will add an entry in the jmx-console-users.properties (depends on JBoss type).
-For JBoss org, this will enable security in jmx-console since the enterprise versions have
-jmx-console security by default.
-
-### Configuring datasources
-
-Use a "datasource" component
-
-Configuration:
-
-:folder => a folder where this datasource will be saved (default: $JBOSS_HOME/server/$CONFIG/deploy)
-if a relative path is given, it will be appended to default value
-:encrypt => a flag to indicate if the password should be encrypted (default: false)
-:type => the type of the datasource
-:name => a name for saving the file (default: :type)
-:attributes => a Hash with the attributes that will be changed in template (the only required is :jndi_name)
-
-Any attribute that is not present in datasource xml will be created using this template: <key>value</key>.
-
-For converting the symbol attributes, the above rules are used taking by example a
-value ":database_url":
-
-1. The value "database_url"
-2. The value "database-url"
-3. The value "DatabaseUrl"
-4. The value "DATABASE_URL"
-
-The key for finding the correct datasource is the configuration attribute :type, which is
-used to search in $JBOSS_HOME/docs/examples/jca for the file.
-
-Any key that is not found in the datasource template will be added. If it is a Symbol,
-the underlines will be converted to hyphens.
-
-For saving the file, the configuration :name will be used in the form "${name}-ds.xml".
-
-Example:
-
-    - datasource:
-        :type: postgres
-        :attributes:
-            :user_name: postgres
-            :password: postgres
-            :connection_url: jdbc:postgresql://localhost:5432/sample_database
-            :min_pool_size: 5
-            :max_pool_size: 15
-
-### Replacing hypersonic
-
-The same as Datasouce, but use the "default_ds" component instead.
-
-    - default_ds:
-        :type: postgres
-        :attributes:
-            :user_name: postgres
-            :password: postgres
-            :connection_url: jdbc:postgresql://localhost:5432/jboss_db
-            :min_pool_size: 5
-            :max_pool_size: 15
-
-This will change the DefaultDS mapping to the desired datasource. Since JBoss SOA-Platform
-already have a tool to do the work, it will be called with the correct mapped options
-(see the file $SOAP_HOME/tools/schema/build.properties for the supported options)
-
-    - default_ds:
-        source.dir: postgresql84
-        db.name: jboss_soap_db
-        db.hostname: localhost
-        db.port: 5432
-        db.username: postgres
-        db.password: postgres
-        db.minpoolsize: 5
-        db.maxpoolsize: 15
-
-### Installing mod_cluster
-
-Use a "mod_cluster" component
-
-Configuration:
-
-:path => where the mod_cluster.sar is located
-:folder => where the mod_cluster.sar should be installed (default: $JBOSS_HOME/server/$CONFIG/deploy)
-
-The additional configurations are the entries in the bean ModClusterConfig (mod_cluster-jboss-beans.xml)
-and can be in a String form (using the entry name) or in a Symbol form (using ruby nomenclature - :sticky_session)
-
-### Configuring run.conf
-
-### Slimming
-
-Use a "slimming" component.
-
-Configuration:
-
-Use an array with the services to remove, the current supported are:
-
-* Admin Console       => :admin_console
-* Web Console         => :web_console
-* Mail Service        => :mail
-* BeanShell           => :bean_shell
-* Hot Deploy          => :hot_deploy
-* UDDI                => :uddi
-* UUID Key Generator  => :key_generator
-* Scheduling          => :scheduling
-* JMX Console         => :jmx_console
-* JBoss WS            => :jboss_ws
-* JMX Remoting        => :jmx_remoting
-* ROOT Page           => :root_page
-* Management          => :management
-* IIOP                => :iiop
-* JBoss Web           => :jboss_web
-* SNMP                => :snmp
-* Profile Service     => :profile
-* EJB3                => :ejb3
-* EJB2                => :ejb2
-* JMX Invoker         => :jmx_invoker
-* HA HTTP Invoker     => :ha_http_invoker
-* Legacy Invoker      => :legacy_invoker
-* Transaction         => :transaction
-* Remoting            => :remoting
-* Properties Service  => :properties
-* Database/Datasource => :database
-* JSR-88              => :jsr88
-* XNIO                => :xnio
-
-Any slimmed service will be removed logically by using a ".rej" suffix in the files/directories.
-
-Tools
------------
-
-### Command Line Slimming
-
-You can do a slimming using only the command line, just put your terminal in the profile dir
-and do the following:
-
-    rboss-profile --this --slimming services-here
-
-This will slim the defined services. Use --verbose to see the changed files.
-
-To restore slimmed services, use --restore.
-
-    rboss-profile --this --restore services-here
-
-### Password Encryption
-
-You can use the SecureIdentityLoginModule to encrypt a password for use with a login module
-to secure a datasource password.
-
-    rboss-profile --encrypt your-password-here
-
+* `/lib/rboss/view/colorizers.rb`
+* `/lib/rboss/view/formatters.rb`
+* `/lib/rboss/view/health_checkers.rb`