Start setting up some infrastructure for Bundle Groups and associated
permissions.
Work in progress - getting new bundle perms integrated into role views
Move the restart operation to the plugin rather than server bean. This simplifies the interface between the server bean and storage node plugin.
Add support for updating the JMX Port. The process sends a restart to the resource last to avoid putting the Server in maintenance mode.
Make CassandraNodeComponent shutdown operation wait for server to go down (unless running on OSX)
BZ 974963 Allow to schedule operations that have no parameters.
Add a LinkSerializer to send links in correct format (one could argue not to send links at all).
Make the parser check its input and bail out if it is not valid.
Bug 886126 - Datasource JNDI change takes too long to be propagated to JON server

In EAP5, JNDI name is the key of Datasource and Connection Factory managed components. Consequently, there is no way to change the JNDI name of such components without creating a new managed component, which will in the end be discovered by RHQ.

So in RHQ, jndi-name config property is now marked as read-only (it will still be required when creating a Datasource or a Connection Factory).
More work on working new bundle group stuff into role edit view. Also, continued
cleanup of Messages.properties.
[BZ 988574] - Consolidated Metrics Screen - UXD Redesign
Operations are now created in a new transaction. Also, change the way the configuration is updated.

The steps for a full configuration update:
1) Invoke config update operation on the plugin
2) Update the JMX port on the storage node entity
3) Restart the storage node server
4) Update the connection settings for the storage node if JMX port changed
upgrade to version 1.0.2 of datastax driver
check cluster status using cql driver instead of using jmx

The server had been polling storage cluster nodes with a jmx call to make sure
that at least one node is up for client requests. If no nodes are up, then the
server goes into maintenance mode.

That check is no longer done with a quartz job using jmx. It is now performed
with event notifications we receive from the cql driver. This means that the
server no longer has to care about storage node jmx ports. This has a couple
benefits. First, it reduces the complexity involved with changing the jmx port.
Secondly, since the server no longer is making jmx calls to storage nodes, the
port can be locked down to localhost access.

Any server side code that needs access to the driver's Session should instead
use the new StorageSession class. StorageSession provides the same API, and it
also encapsulates the event handling/propagation logic that is necesary for
monitoring the cluster availability.
Put the real version in here, as otherwise we have a circular dependency.
Start of remote API design/impl for BundleGroups
trivial change - first commit from intellij :}
add some javadoc and new apis for bundle groups
add storage node shutdown operation that uses pid file

There can be problems with getting the actual, current pid from Sigar, so the
storage node plugin will first attempt to get the pid from the pid file which
should exist on disk. If that fails, then we will attempt to get the pid from
Sigar.

This implementation for shutdown does not work for Windows so need to revist it
to add in Windows support. We may even consider delegating to rhqtcl.
add createInitialBundleVersion APIs