wildfly-messaging-activemq_1_0.xsd

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
[WFLY-6816] Add missing attribute

[WFLY-6077] address-settings's auto-create|delete-jms-queues

Add auto-create-jms-queues and auto-delete-jms-queues attributes to

address-settings resource.

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

  1. … 6 more files in changeset.
[WFLY-5888] Add journal-pool-files attribute

Artemis 1.1.0.wildfly-010 has a new attribute journal-pool-files to

control the number of journal files that can be reused.

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

  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-5554] Fix jms-bridge XSD attributes

* flag jms-bridge's XSD attributes that do not allow null in the

management model as required.

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

[WFLY-5488] Support managed-connection-pool & enlistment-trace attributes

* add managed-connection-pool and enlistment-trace attributes to the

pooled-connection-factory resource

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

  1. … 7 more files in changeset.
[WFLY-5446] Support connection to older messaging servers

* add the protocol-manager-factory to the connection-factory and

pooled-connection-factory resources.

This property can be used to specified a different protocol manager

factory than the default Artemis one. For example, it allows to use a

HornetQ client protocol manager factory so that an Artemis client can

connect to a HornetQ server

* add artemis-hornetq-protocol dependency to wildfly-jms-client BOM so

that a WildFly JMS client using Artemis can connect to a HornetQ

server. Java Serialization does not work in that case (HornetQ classes

can not be deserialized by Artemis) so the client must use client-side

JNDI to identify the JMS resources to lookup.

* remove org.hornetq client libs from wilfly-jms-client. Now that

Artemis supports connecting to HornetQ server, there is no need to

bundle HornetQ clients.

* flag org.hornetq.client module as private. It is only used to provide

legacy JMS resources that can be looked up by older WildFly clients

that were bundling HornetQ client libs.

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

  1. … 7 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.
Revert "[WFLY-4902] Upgrade to Artemis 1.1.0-wildfly-1"

    • -31
    • +9
    ./wildfly-messaging-activemq_1_0.xsd
  1. … 13 more files 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

    • -18
    • +27
    ./wildfly-messaging-activemq_1_0.xsd
  1. … 3 more files in changeset.
[WFLY-4867] Improve Artemis interceptor support

Update the server resource with 2 attributes, incoming-interceptors

and outgoing interceptors that are both a LIST of OBJECT (composed of 2 STRING attributes, name and module).

These attributes are then processed and corresponding classes are instantiated and passed

to Artemis ServiceRegistry.

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

    • -8
    • +22
    ./wildfly-messaging-activemq_1_0.xsd
  1. … 8 more files in changeset.
[WFLY-4867] Improve Artemis interceptor support

Update the server resource with 2 attributes, incoming-interceptors

and outgoing interceptors that are both a LIST of OBJECT (composed of 2 STRING attributes, name and module).

These attributes are then processed and corresponding classes are instantiated and passed

to Artemis ServiceRegistry.

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

    • -8
    • +22
    ./wildfly-messaging-activemq_1_0.xsd
  1. … 8 more files in changeset.
[WFLY-4902] Upgrade to Artemis 1.1.0-wildfly-3

* udpate cluster-connection resource, forward-when-no-consumers has been

replaced by message-load-balancing -type attribute

* upgrade to artemis-wildfly-integration 1.0.2-wildfly-1

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

  1. … 8 more files in changeset.
[WFLY-4902] Upgrade to Artemis 1.1.0-wildfly-5

* udpate cluster-connection resource, forward-when-no-consumers has been

replaced by message-load-balancing -type attribute

* upgrade to artemis-wildfly-integration 1.0.2-wildfly-1

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

  1. … 8 more files in changeset.
[WFLY-4585] Provide JMS forward compatibility

* add support for JMS forward compatibility so that legacy JMS clients

(with HornetQ client libraries) can lookup HornetQ-based JMS resources

from JNDI and connect to the Artemis server using its HORNETQ

protocol.

* for JMS destinations (jms-queue and jms-topic), a new attribute

legacy-entries can be used to bind the HornetQ-based destinations to

JNDI.

* for connection factories, a new resource (legacy-connection-factory)

has been added. It is different from the connection-factory resource

used by Artemis client.

* add org.hornetq.client module. The messaging-activemq subsystem depends

on it to create HornetQ managed resources for forward interoperability.

* add test for legacy (HornetQ) clients connecting to resources managed

by the messaging-activemq subystem

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

    • -12
    • +60
    ./wildfly-messaging-activemq_1_0.xsd
  1. … 36 more files in changeset.
[WFLY-4584] new messaging-activemq subsystem

* add Maven GAVs for ActiveMQ Artemis artifacts

* add new messaging-activemq subsystem based on the legacy messaging

subsystem and using Artemis code instead of HornetQ

* update test to use urn:jboss:domain:messaging-activemq:1.0 namespace

* add ActiveMQ Artemis client artifacts to jms client

* add org.jboss.activemq.artemis.integration:activemq-wildfly-integration artifact

* use service extension to bind with Artemis's transaction manager locator and recovery manager

* add (core) queues addition/removal to JMSOperations

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

    • -0
    • +706
    ./wildfly-messaging-activemq_1_0.xsd
  1. … 280 more files in changeset.