Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
[WFLY-4945] Fix should work for resources with multiple affected attributes.

[WFLY-4945] Check operation value when confirming whether an 'add' op is authorized

  1. … 2 more files in changeset.
[WFLY-3997] Introduce version 2.2 of the management schema and model version.

  1. … 98 more files in changeset.
[WFLY-3993] / [WFLY-3998] Update the model to support specifying enabled-protocols and enabled-cipher-suites for the SSL definition within the security realm.

  1. … 2 more files in changeset.
add missing call to registerNotifications()

  1. … 1 more file in changeset.
override emit(Notification)

to delegate the notification emission to the primary context

Fix incorrect handling of recursive value and return of the 'attributes-only excludes recursive or recursive-depth' validator

Return of setAllowNull to RECURSIVE definition Code simplification in setNextRecursive

Add case "break" for cleanliness - functionality-neutral change

Code cleanup

WFLY-3705, Logic implemented according to bevavioral tables

1) Recursive decision and value propagation is isolated

2) Attribute validators changed

3) ReadResourceHandler no longer manipulates its own validators, but uses the ones in the definition

4) ReadResourceDescriptionHandler had yet another version of recursion logic - fix that one as well

5) Update testsuite to check for, hopefully, all conditions

  1. … 1 more file in changeset.
[WFLY-266] Notification support

* Refactor the registry for the notification handlers by splitting the map

into path segments to mitigate the o(n) cost.

* Rename the registry to NotificationHandlerRegistry and move it to the

org.jboss.as.controller.registry package (leveraging the

AtomicFieldUdpated of the package too)

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

9.x PR: https://github.com/wildfly/wildfly-core/pull/95

  1. … 10 more files in changeset.
Remove unnecessary if branch - rrOp object is empty anyway

Add another recursive handling piece of logic to try to make this work

WFLY-3705 read-resource recursive-depth has no effect

[WFCORE-28] Add global resource notifications

Runtime attributes does not store their values in the resource models

and their read handler must be called before and after their write

handler to get the old and new value of the attribute.

JIRA: https://issues.jboss.org/browse/WFCORE-28

9.x PR: https://github.com/wildfly/wildfly-core/pull/62

  1. … 1 more file in changeset.
[WFCORE-28] Add Global Resource Notifications

* add global notifications for resources:

* resource-added when a resource is added to the management model

* resource-removed when a resource is removed from the management

model

* attribute-value-written for resources that allow to write

attributes when an attribute value is successfully changed.

This notification contains a data set composed of:

* name - the name of the attribute that has been changed

* old-value - the value of the attribute before it was changed

* new-value - the value of the attribute after it was changed

The old-value and new-value are *not* resolved (an attribute that is

undefined and has a default value will return "undefined" as its

old-value).

JIRA: https://issues.jboss.org/browse/WFCORE-28

9.x PR: https://github.com/wildfly/wildfly-core/pull/45

  1. … 10 more files in changeset.
[WFLY-1857] Deprecate 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

9.x PR: https://github.com/wildfly/wildfly-core/pull/23

    • -0
    • +93
    ./org/jboss/as/controller/NotificationDefinition.java
  1. … 49 more files in changeset.
Core split: Remove all non-core modules, add dependencies on org.wildfly.core artifacts

    • -39
    • +0
    ./org/jboss/as/controller/BootContext.java
  1. … 3438 more files in changeset.
Merge pull request #5681 from emuckenhuber/WFLY-547

[WFLY-547] track uncleanly unregistered slave hosts

  1. … 2 more files in changeset.
WFLY-3478 fixing mask verification

  1. … 1 more file in changeset.
WFLY-3478 fixing mask verification

  1. … 1 more file in changeset.
[WFLY-3090] Ensure the latch gets counted down

Add missing space in message

[WFLY-3162] Add reconnect timeout and logic to syslog tcp and tls protocols

  1. … 12 more files in changeset.
Remove #registerMetric(String attributeName, OperationStepHandler metricHandler, EnumSet<AttributeAccess.Flag> flags)

  1. … 2 more files in changeset.
Remove #registerMetric(String attributeName, OperationStepHandler metricHandler)

  1. … 2 more files in changeset.
Remove #registerReadOnlyAttribute(String attributeName, OperationStepHandler readHandler, EnumSet<AttributeAccess.Flag> flags)

  1. … 2 more files in changeset.
Remove #registerReadWriteAttribute(String attributeName, OperationStepHandler readHandler, OperationStepHandler writeHandler, EnumSet<AttributeAccess.Flag> flags)

  1. … 2 more files in changeset.