Clone Tools
  • last updated a few minutes ago
Constraints: committers
Constraints: files
Constraints: dates
[WFLY-13390]:migrate operation on legacy messaging subsystem fails with WF19.

* Adding a warning if no connector is defined in a broadcastgroup


  1. … 3 more files in changeset.
[WFLY-10339]: Broadcast/discovery-group resources have ambiguous requirement specs.

* Adding 6 new resources to have specific boradcast and discovery groups

using socket-bindings or cluster connections

* Updating the schema for these new resources

* Requires connectors for broadcast-group resource


  1. … 79 more files 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.


  1. … 2 more files in changeset.
Add messaging subsystem transformers for EAP 6.4 and minimize deprecated api usage

  1. … 9 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.


  1. … 3 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


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



  1. … 2 more files in changeset.
Merge pull request #8226 from jmesnil/WFLY-5458_jgroups_stack_not_allow_expressions

[WFLY-5458] Do not allow expressions for jgroup-stack and groups-channel attributes

  1. … 1 more file 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.


  1. … 2 more files in changeset.
[WFLY-5526] Migrate forward-when-no-consumers attribute

Warn if the attribute is using an expression (and discard it).

Otherwise change it to the message-load-balancing-type according to

Artemis documentation at


  1. … 3 more files in changeset.
[WFLY-5458] Do not allow expressions for jgroup-stack and jgroups-channel attributes

These attributes may reference other management resources (cf. WFLY-5189) and must not

allow expressions.


  1. … 2 more files in changeset.
[WFLY-5384] Validate Artemis Parameters

* map WildFly hyphen-separated names to Artemis CamelCase names for

acceptor/connectors parameters

* change http-upgrade-endpoint to be a required attribute for http-connector resource


  1. … 10 more files in changeset.
[WFLY-5086] Messaging HA migration

* migrate the HA configuration of the legacy messaging servers when it

is possible to determine its state.

* if shared-store or backup attributes hold expressions, there is no way

to determine the actual HA configuration of the server in domain mode.

In that case, the HA configuration is discarded and the user is


* In other case, a ha-policy resource is created for the migrated server

of the new messaging-activemq subsystem.


    • -0
    • +43
  1. … 3 more files in changeset.
[WFLY-5014] jms-bridge context properties can not be parsed

* fix jms-bridge's source-context and target-contex attribute


* add a jms-bridge element to the legacy messaging configuration test

used to check its migration


  1. … 3 more files in changeset.
[WFLY-4960] Discard interceptors during messaging migration

HornetQ-based interceptors can not be loaded by Artemis.

Discard them during the migration operatin and warn the user that

he must implement them using the Artemis base type instead.


  1. … 3 more files in changeset.
[WFLY-4856] messaging: fix types of attribute's default values

This fixes the testTransformersEAP_X_X_X failures introduced by

WFLY-4831 - Clean up HornetQ modules


  1. … 7 more files in changeset.
[WFLY-4594] move messaging subsystem to legacy/


  1. … 458 more files in changeset.
[WFLY-4587] Messaging migrate management operation

add :migrate operation to legacy messaging subsystem


    • -0
    • +474
  1. … 11 more files in changeset.