Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
[WFCORE-4257] Replace RemotingModelControllerClient finalizer with a PhantomReference

[WFCORE-4257] Replace RemotingModelControllerClient finalizer with a PhantomReference

[WFCORE-4152] HC cannot connect to DC after lost connect if models are out of sync and RBAC is enabled

Minor refactor for the in vm call

[WFCORE-4152] Test Case HC cannot connect to DC after lost connect if models are out of sync and RBAC is enabled

  1. … 13 more files in changeset.
[WFCORE-4152] HC cannot connect to DC after lost connect if models are out of sync and RBAC is enabled

Minor refactor for the in vm call

[WFCORE-4152] Test Case HC cannot connect to DC after lost connect if models are out of sync and RBAC is enabled

  1. … 13 more files in changeset.
[WFCORE-3397] Introduce new thread pool to (deprecated) model controller client configuration factory

[JBEAP-12818] Add translations

  1. … 264 more files in changeset.
[WFCORE-3195] Deprecate the authentication configuration URI settings in the ModelControllerClientConfiguration.

[WFCORE-3145] Comment out unused logger methods

  1. … 19 more files in changeset.
[WFCORE-3034] Delay the default SSLContext initialisation until we know it is required.

  1. … 3 more files in changeset.
[WFCORE-2946]: Unifiying the 3 FileStreamEntry definitions

[WFCORE-2946]: Errors publishing a large deployment to a remote server.

Modifying the API so that we may use a java.nio.file.Path instead of a InputStream thus removing the need to read the full input to get its length.

  1. … 1 more file in changeset.
[WFCORE-2769] Allow the user to define an authentication configuration when creating a ModelControllerClient.

  1. … 3 more files in changeset.
[WFCORE-2705] Block when closing the RemotingModelControllerClient until it's resources have been closed.

[WFCORE-2668]: Explode content with DeploymentPlan doesn't work properly

The operation wasn't properly executed

Adding some tests

  1. … 1 more file in changeset.
[WFCORE-2628]: DeploymentPlan doesn't have an operation to explode content.

Adding an operation to be able to explode sub-content as only the root deployment could be exploded.

[WFCORE-1507] Expose in-vm ModelControllerClient creation via a capability Addresses [WFCORE-1964] by having clear contracts for whether an internal client should always execute with 'SuperUser' RBAC perms Also addresses [WFCORE-2327] by creating a standardized way of establishing a client that acts as SuperUser

  1. … 23 more files in changeset.
[WFCORE-2228] Convert legacy Subject reading and writing to work with a SecurityIdentity and InetAddress.

The protocol remains compatible with legacy hosts that may be managed by newer domain controllers, in that situation it will still be restored as a Subject.

  1. … 20 more files in changeset.
[WFCORE-714] Prevent RemotingModelControllerClient from being able to close the Remoting management endpoint

[WFCORE-296]: Switch URI scheme from remoting:// http-remoting:// https-remoting:// to remote:// remote+http:// and remote+https://

Changing also the URL format for JMX and the default protocol is schemas.

  1. … 56 more files in changeset.
[WFCORE-610] Prevent an UnsupportedOperationException from being thrown when attempting to close an UncloseableEndpoint

  1. … 1 more file in changeset.
[WFCORE-952] Use standard null checks

  1. … 1 more file in changeset.
[WFCORE-1157] listener API for process state changes

* add API to let user be notified of process state changes by adding a

class to the resource process-state-listeners in the core-management subsystem.

* add by default the core-management subsystems to the standalone and

domain subsystem templates.

* split the core-management module in 2 parts : client and subsystem.

* one service per listener

* add a specific JMX notifier that listens on RuntimeConfigurationState and RunningState changes : RunningStateJmx.

* basic documentation.

* small fix for ModuleOpsCompletionTestCase

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

  1. … 84 more files in changeset.
Revert "[WFCORE-1541] Make controller client executor lifecycle controllable"

This reverts commit 62ce5944d488399500494a89c2536a7423299675.

Going forward we may not actually want to support having people provide their own executor, so, since making it configurable has never been in a .Final release lets not expose it now.

Revert "[WFCORE-1541] Make controller client executor lifecycle controllable"

This reverts commit 62ce5944d488399500494a89c2536a7423299675.

Going forward we may not actually want to support having people provide their own executor, so, since making it configurable has never been in a .Final release lets not expose it now.

Revert "[WFCORE-1541] Make controller client executor lifecycle controllable"

This reverts commit 2623beaad3d3e5cc9e606855b4cff7ce4268ee73.

Going forward we may not actually want to support having people provide their own executor, so, since making it configurable has never been in a .Final release lets not expose it now.

[WFCORE-1618] Drop use of ProtocolChannelClient which is just an odd way to implement some factory methods Also standardize on ProtocolConnectionConfiguration instead of the ProtocolChannelClient.Configuration subclass which brings no added functionality

  1. … 12 more files in changeset.
[WFCORE-1618] Clarify ManagementClientChannelStrategy use by not having ManagementChannelHandler create its own strategy It's helpful to know which classes are using ManagementClientChannelStrategy.Existing

  1. … 6 more files in changeset.
Move main code and tests to new Remoting 5 based APIs

  1. … 11 more files in changeset.
[WFCORE-1573] Avoid possible hangs due to synchronous closure of the Endpoint

[WFCORE-1573] Avoid possible hangs due to synchronous closure of the Endpoint