Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
[WFLY-12417] Remove unneeded subsystem transform tests to EAP < 6.4

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

Jira:

https://issues.jboss.org/browse/WFLY-10339

https://issues.jboss.org/browse/WFLY-6607

https://issues.jboss.org/browse/WFLY-11005

  1. … 78 more files in changeset.
[WFLY-11179]: Messaging http-acceptor should expose a capability and use it to control dependencies.

* Adding a capability and a requirement on http-upgrade-registry

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

  1. … 4 more files in changeset.
[WFLY-11179]: Messaging http-acceptor should expose a capability and use it to control dependencies.

* Adding a capability and a requirement on http-upgrade-registry

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

  1. … 4 more files in changeset.
JBEAP-8666 Fix tests to work with proper undertow model validation

  1. … 18 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.
legacy messaging transformers - non deprecated api

WFLY-7711 Make AbstractSubsystemBaseTest#testSchemaOfSubsystemTemplates opt-in as opposed to flooding reports with @Ignored tests (WFCORE-1677)

  1. … 28 more files in changeset.
WFLY-6901 - Enable checkstyle for test code

- fix all problems found by checkstyle

  1. … 67 more files in changeset.
WFLY-6602 Expose JGroups channels and channel factories as capabilities. Replace ServiceName factories with equivalent capability/requirement ServiceName factories.

  1. … 112 more files in changeset.
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. … 1 more file in changeset.
Enable default testing of subsystem describe ops

  1. … 6 more files in changeset.
[WFCORE-1353] Disable check that describe fails

  1. … 6 more files in changeset.
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. … 13 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. … 1 more file 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.

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

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

http://activemq.apache.org/artemis/docs/1.1.0/clusters.html#configuring-cluster-connections

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

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

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

  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

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

  1. … 10 more files in changeset.
[WFLY-5380] Do not create legacy connection factory using in-vm connector

Artemis in-vm connectors are not compatible with HornetQ ones.

Instead of creating legacy-connection-factory that would generate errors

during reload, discard it and add a warning.

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

  1. … 2 more files in changeset.
[WFLY-5084] Warning for unmigrated discovery-group attributes

Add migration-warnings when discovery-group attributes can not be be

migrated.

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

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

warned.

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

of the new messaging-activemq subsystem.

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

    • -0
    • +43
    ./resources/org/jboss/as/messaging/test/subsystem_migration_ha.xml
  1. … 2 more files in changeset.
[WFLY-5083] Warning for unmigrated broadcast-group attributes

Add migration-warnings when broadcast-group attributes can not be be

migrated.

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

  1. … 3 more files in changeset.
Make MessagingExtension extends AbstractLegacyExtension

fix tests to run in ADMIN_ONLY_HC mode.

  1. … 1 more file in changeset.
[WFLY-5014] jms-bridge context properties can not be parsed

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

definitions.

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

used to check its migration

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

  1. … 3 more files in changeset.