BZ 1144238 - update DataStax driver to latest 1.0.8 release
Bug 1140637 - JBoss layered product (JBoss Fuse) does not have direct option
to open new support case

Allow opening support case on JBossFuse : JBossFuseContainer resource types
Bug 1139684 - eap cli script does not get correct result code for eap domain server on windows

This is due to "WFLY-3578 jboss-cli.bat always exits with return code 0 even after a cli failure"
https://issues.jboss.org/browse/WFLY-3578

Added jboss-cli-wrapper.bat
Calling "cmd /c jboss-cli.bat" will always return 0 even if an error occurs in the CLI
Calling it through the wrapper solves the issue

Side work:
* fix standalone and domain startup: start script prefix, if set, was not added
* when an error occurs, execute command and execute script operations now copy process output into the operation result instead of the error message
* some code cleanup (avoid possible NPE)
Bug 1140578 - [eap6 patching] applying patches via bundles fails for Windows - wrong file path extracted

Use hash sign as separator instead of pipe.

Tested on Windows2008R2
An attempt to fix the intermittent failures for
AvailabilityProxyConcurrencyTest.testConcurrentAvailChecks().  I believe the
issue is that depending on random ordering, we could exceed our set timeout
for the synchronous avail check, which we don't want to do in this test. I
added a bit more console output to help diagnose a failure in the future.
[BZ 1144514] No need to remove non-deployed property files from bundle
temporary location before deployment.

This was a remnant of an abandoned approach to the functionality that is
not needed anymore.
[1108168] storage node name in cluster alerts is null
Ensure async initialization complete before rendering
[BZ 1144467] [BZ 1144477] Boolean with null value is a bad idea, if we could not find the port, then we could not check if the agent was running either, so setting it to default false.
Bug 1144452 - "Open Support Case" must support all layered products

Enable Opening support cases for Tomcat Server resources. We cannot detect
EWS version from Tomcat resources, when opening a case on Tomcat resource
only product can be selected properly.

Properly forward Product Name and Product version to RHA for BRMS and
Portal.
fix test that fails on jenkins upgrade jobs
[BZ 1141982] Readonly required props with defaults forced to same values
during bundle deployment.

In the case of new resource creation where the user has the
ability to enter an initial value for a readonly property. This is
not true with bundle deployment because the configuration object is
populated with the default values straight away. This is to make it
possible for the server-side bundle plugin to pass on some
information to the agent-side bundle handler.

This fix ensures that an update of such readonly property is not
possible either through UI or remote API.

In remote API we simply check the supplied deployment configuration
more rigorously, disallowing changes of any readonly properties from
the default values provided by the deployment configuration definition.

The UI had a clever logic of reusing configuration properties used
with the currently live deployment (if any). This approach generally
worked but was also updating readonly properties with the values
coming from the live deployment which is a wrong thing to do if we
understand the readonly props as a way of defining additional
metadata about the bundle version generated by the server-side plugin.
These should always be relevant to the bundle version being deployed
and not taken over from a deployment of some previous bundle version.
[BZ 1136945] Purge/revert of EAP patch bundles works more sanely.

To implement this reasonably, we started tracking the state of
patch bundles deployed through RHQ in external file, located under
the target Wildfly/EAP server's .installation/.rhq subdirectory (the
.installation directory is used by Wfly/EAP itself to keep track of
patching, so it is a logical place to add patching related information).

During deployment we determine the effective set of patches that were
applied from the patch file (by comparing histories before and after
deployment). We then use this information to revert/purge only the
patches that were deployed using RHQ. This information is stored per
destination in the above mentioned metadata directory (so that multiple
destinations per EAP are supported (even though such arrangement is
non-sensical)).

In another words all patches applied before a first patch bundle was
deployed through a destination are retained after a bundle purge and
the revert or purge of the bundle will fail or warn if the history
of patch deployment is unexpected (due to external patch rollbacks
or applications).

The revert/purge will fail if no patches can be rolled back due
to the state of the history having a different "tip" than expected.
A warning is emitted to the audit log if some of the patches that
were expected to rollback couldn't be because of some other change
in the patch application history.

There situations will only exist if the EAP server is patched through
other means than RHQ after it has been patched using RHQ thus creating
and inconsistency between what RHQ sees as the deployment history of
the destination and the real state on the EAP resources.
[BZ 1069547] Adding "Active Patches" trait to Host ctl & Standalone svr

As such, the user now has the overview of the patches applied to the
individual Wfly/EAP servers in their env. This complements the bundle
subsystem from which the same information could be deduced, too,
under the assumption that RHQ server would be the sole "issuer" of
the patches to the servers.
[BZ 1070277] - (JON3-39) JON should (be able to) block login to a user without roles - Changing the default of the property to true, i.e. enabling the login for user without roles by default.
[BZ 1145101] - Email alert notification field 'Condition' contains characters which are not part of defined condition - Changing AlertManagerBean.prettyPrintAlertCondition() method to incorporate the changes in alert condition instance for events (the option field is used to carry two regular expression; one for the event details and one for the event source path).
[BZ 1084056] Added missing policy to the "Anty Entropy Sessions" type (a single bean) to allow users to configure the behaviour of a missing resourece after a Cassandra or Storage Node server restart
Merge pull request #127 from genman/BZ1144238

BZ 1144238 - update DataStax driver to latest 1.0.8 release
Work related to test failure in AvailabilityProxyConcurrencyTest
- Two changes to AvailabilityProxy itself
  - make AvailabilityProxy.getAvailability() a synchronized method. We don't
    want two threads calling this concurrently. This is not too likely
    in production, given intervals between checks, but may have been possible
    when performing a live check. The test code on the other hand was
    sometimes failing due to parallel execution of the call.
  - stop AvailabilityProxy.getAvailability() from converting UNKNOWN to
    DOWN when the avail check is asynchronously in progress.  This breaks the
    contract as stated in the javadoc and could lead to false DOWN reporting.
    (although, conversely, now fixed it could take longer for valid DOWN to
    be reported, as a check may need to timeout).
- unrelated but update AvailabilityFacet javadoc to add in valid MISSING state
om>
- work on the test code. replace the concurrent thread approach with the more
  realistic serialized calls and change timing around to more predictably
  mix some calls that complete synchronously and some that complete
  asynchronously.
[BZ 1140578] Change the patch name delimiter also on the agent-side.
BZ 1129729 - catch any exceptions if a plugin failed to be processed during detection - this should allow the rest of the plugins to continue to be processed.