Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
[WFLY-12284] Replace 'new ModelNode().set(0)’ with 'ModelNode.ZERO’

    • -1
    • +1
    ./jms/ConnectionFactoryAttributes.java
  1. … 2 more files in changeset.
[WFLY-12284] Replace 'new ModelNode().set(false)’ with 'ModelNode.FALSE’

    • -7
    • +7
    ./jms/ConnectionFactoryAttributes.java
  1. … 6 more files in changeset.
[WFLY-12284] Replace 'new ModelNode().set(true)’ with 'ModelNode.TRUE’

    • -3
    • +3
    ./jms/ConnectionFactoryAttributes.java
  1. … 4 more files in changeset.
[WFLY-12284] Replace 'new ModelNode(true)’ with 'ModelNode.TRUE’

  1. … 75 more files in changeset.
[WFLY-12284] Replace 'new ModelNode(false)' with 'ModelNode.FALSE'

  1. … 83 more files in changeset.
WFLY-12150: make attributes with default values optional

  1. … 2 more files in changeset.
[WFLY-11949] Eliminate unneeded dependencies from the legacy messaging subsystem pom and module.xml

Also clean out unneeded code, including switches that can be simple if/else blocks.

    • -39
    • +31
    ./Messaging13SubsystemParser.java
    • -147
    • +92
    ./MessagingSubsystemParser.java
    • -19
    • +0
    ./jms/ConnectionFactoryAttribute.java
  1. … 2 more files in changeset.
WFLY-9601 upgrade version of checkstyle to latest

  1. … 35 more files in changeset.
[WFLY-9190] Comment out unused logger methods

    • -464
    • +454
    ./logging/MessagingLogger.java
  1. … 22 more files in changeset.
[WFLY-9176] Don't do a recursive readResourceFromRoot to inspect the names of children

  1. … 16 more files in changeset.
[WFLY-8928] Allow local transactions for JMS RA session

By default, a JMS session created from a RA does not allow local

transactions (as specified by the JMS 2.0 API).

However, for legacy compatibility, this behaviour can be changed by

setting the allow-local-transactions attribute to true on the

pooled-connection-factory resource.

During migration of the legacy messaging subsystem, this attribute

is set to true to preserve the behaviour of HornetQ RA that was

allowing local transactions.

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

  1. … 19 more files in changeset.
[WFLY-8849] The describe-migration ops are read-only

  1. … 2 more files in changeset.
[WFLY-8849] The migration ops are not runtime-only

  1. … 2 more files in changeset.
WFLY-7576 stop using deprecated setAllowNull in favour of setRequired

    • -15
    • +15
    ./ClusterConnectionDefinition.java
    • -1
    • +1
    ./ConnectorServiceParamDefinition.java
  1. … 77 more files in changeset.
WFLY-7576 Don't use deprecated no-op OperationContext#stepCompleted()

    • -1
    • +0
    ./AlternativeAttributeCheckHandler.java
    • -1
    • +0
    ./HornetQServerResourceDefinition.java
  1. … 64 more files in changeset.
WFLY-7728 - Lazy load legacy messaging parsers

- don't use static instances

[WFLY-6504] Fix messaging migration warnings

Clarify migration warnings to emphasis whether something can not be

migrated *from* a legacy resource or *to* a new resource.

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

Merge pull request #8659 from jmesnil/WFLY-6068_failback_delay_warning

[WFLY-6068] Migration warning for failback-delay

  1. … 1 more file in changeset.
[WFLY-6068] Migration warning for failback-delay

Discard the failback-delay from the server's add operation during

migration (and not from the ha-policy's add).

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

  1. … 1 more file in changeset.
[WFLY-6125] Migration warning for remoting-interceptors

During migration, discard (deprecated) remoting-interceptors attribute

and a migration-warnings that these interceptors must be updated to use

the Artemis interceptor base class instead of the HornetQ one.

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

  1. … 2 more files in changeset.
[WFLY-6068] Migration warning for failback-delay.

Warn that the failback-delay attribute is not migrated as Artemis

detects failback in a deterministic way.

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

[WFLY-6027] Fix messaging migration warnings

Fix typos

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

[WFLY-5678] Do not migrate attributes that no longer accept expressions

Reword migration warnings so that they are more helpful when displayed

in both :migrate and :describe-migration operations

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

Add messaging subsystem transformers for EAP 6.4 and minimize deprecated api usage

  1. … 5 more files in changeset.
[WFLY-5709] Fix Messaging HA configuration

* the shared-store-colocated configuration creates replication

live/backup configuration instead of shared-store ones.

* live and backup configuration must always be created for colocated

configurations.

* remove failback-delay attribute that is ignored in Artemis since

1.0.0.wildfly-008

* add attribute initial-replication-sync-timeout to specify

deterministically how long to wait for the initial replication.

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

  1. … 12 more files in changeset.
[WFLY-5667] Migration: do not migrate parameters ignored by new subsystem

During migration, do not migrate the use-nio parameter for remote/http

connector/acceptor resources in the new messaging-activemq subsystem and

add a warnings to the :migrate operation result.

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

  1. … 2 more files in changeset.
[WFLY-5678] Do not migrate attributes that no longer accept expressions

The discovery-group and broadcast-group resources in the legacy

messaging subsystem accept expressions for their jgroups-stack and

jgroups-channel resources.

The same resources in the new messaging-activemq subsystem no longer

accepts expressions for them (as they are references to other model

resources).

During migration, these attributes are ignored and removed from the new

:add operations to create the messaging-activemq resources and warnings

are added to the migration-warnings.

This allows the :migrate operation to succeed and the user will have to

fix the model afterwards by specifying a correct value for these

attributes.

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

  1. … 2 more files in changeset.
[WFLY-5548] Migrate backup-group-name attribute

If the legacy hornetq-server has defined a backup-group-name, migrate it

to the new ha-policy resource for replication-master and

replication-slave types.

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

  1. … 2 more files in changeset.
Merge pull request #8287 from jmesnil/WFLY-5533_domain_migrate_with_legacy_entries

[WFLY-5533] Calling :migrate(add-legacy-entries=true) in domain fails

[WFLY-5533] Calling :migrate(add-legacy-entries=true) in domain fails

Read the server resource relative to the context's current address.

This address can can change whether we are in standalone or domain mode

but it always correspond to the messaging subsystem address.

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