[jboss-jira] [JBoss JIRA] (WFLY-9591) Emulate Artemis 1.x address convention

[Miroslav Novak (Jira)]

    [ https://issues.jboss.org/browse/WFLY-9591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13663255#comment-13663255 ] 

Miroslav Novak commented on WFLY-9591:
--------------------------------------

WF14 contains Artemis 2.6.3. Naming convestion is kept with jms prefixes so configuration looks like:
{code}
<address-setting name="#"
                            dead-letter-address="jms.queue.DLQ"
                            expiry-address="jms.queue.ExpiryQueue" />
{code}

Resolving jira.

> Emulate Artemis 1.x address convention
> --------------------------------------
>
>                 Key: WFLY-9591
>                 URL: https://issues.jboss.org/browse/WFLY-9591
>             Project: WildFly
>          Issue Type: Bug
>          Components: JMS
>            Reporter: Jeff Mesnil
>            Assignee: Jeff Mesnil
>            Priority: Major
>             Fix For: 14.0.0.Final
>
>
> Artemis 2.x has changed the naming convention for its resources.
> JMS Queue (resp. topic) no longer uses the "jms.queue." (resp. "jms.topic.") prefix to name its address and core queues.
> In the messaging-activemq subsystem, there are many attributes that correspond to such addresses.
> In the default configuration, we specified addresses for expiry and DLQ in the address-setting resources:
> {code}
> <address-setting name="#"
>                             dead-letter-address="jms.queue.DLQ"
>                             expiry-address="jms.queue.ExpiryQueue" />
> {code}
> This configuration must now be updated to use the new address naming convention:
> {code}
> <address-setting name="#"
>                             dead-letter-address="DLQ"
>                             expiry-address="ExpiryQueue" />
> {code}
> In order to preserve backwards compatibility, we decided to preserve Artemis 1.x address convention for JMS resources created by the messaging-activemq subsystem.
> The user configuration and management code will remain compatible without any change.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)