Don't run patching testsuite by default
[WFLY-1857] Remove ConstrainedResourceDefinition
[WFCORE-2] Let the ReadOnlyContext invoke on the primary context when assertions are enabled
[WFCORE-4] Add RejectAttributeChecker.ALL
[WFCORE-5] Don't leak a ThreadGroup every time we create a ModelControllerClientConfiguration
Don't show redundant/confusing individual attribute/operation data in RBAC constraint applies-to if the entire resource is constrained
Merge pull request #26 from ctomc/testsuite-split

Don't run patching testsuite by default
Merge pull request #35 from bstansberry/WFCORE-5

[WFCORE-5] Don't leak a ThreadGroup every time we create a ModelControll...
Merge pull request #33 from bstansberry/WFCORE-4

[WFCORE-4] Add RejectAttributeChecker.ALL
Merge pull request #32 from bstansberry/WFCORE-2

[WFCORE-2] Let the ReadOnlyContext invoke on the primary context when as...
[WFCORE-7] Don't assume valid inputs to convertParameterExpressions
[WFCORE-8] Avoid 'Operation handler failed: null' message
Merge pull request #36 from bstansberry/redundant-rbac

Don't show redundant/confusing individual attribute/operation data in RB...
Merge pull request #37 from bstansberry/WFCORE-7

Improve some failure messages
Merge pull request #30 from bstansberry/WFLY-1857

[WFLY-1857] Remove ConstrainedResourceDefinition
[WFLY-266] Notification Support

* add notifications to AS7 resources description
  notifications are described in :read-resource-description operation if
  the notifications boolean is true
* NotificationDefinition let any resources describe the notifications
  they can emit by registering them in the ManagementResourceRegistration
* add NotificationRegistry (exposed by the ModelController) to
  register/unregister notification handlers
* add NotificationSupport to emit notifications during a managemenet
  operations (through OperationContext.emit(Notification))

Notifications emitted by OperationContext.emit(Notification) are
effectively sent at the end of the operation execution if it is
successful. This ensure that the order of notifications emitted by a
single OperationContext will be received in the same order (unless they
are emitted during the ResultHandler execuion).

If the NotificationSupport is created with an ExecutorService, the
delivery of notifications is non-blocking and will not block the
remaining code path of the operation execution.

JIRA: https://issues.jboss.org/browse/WFLY-266