[ 
https://issues.apache.org/jira/browse/ARTEMIS-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16350850#comment-16350850
 ] 

ASF GitHub Bot commented on ARTEMIS-1658:
-----------------------------------------

GitHub user mtaylor opened a pull request:

    https://github.com/apache/activemq-artemis/pull/1843

    ARTEMIS-1658 Add prefix option to ActivationSpec

    Artemis 1.x RA would do a core queue lookup if it could not find the
    Destination in JNDI.  We need to ensure that we can support the old
    address model for backwards compatability.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mtaylor/activemq-artemis ARTEMIS-1658

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/1843.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1843
    
----
commit 041373b04ee52c224059edfd1b4bcc54e448e360
Author: Martyn Taylor <mtaylor@...>
Date:   2018-02-01T15:52:25Z

    ARTEMIS-1658 Add prefix option to ActivationSpec
    
    Artemis 1.x RA would do a core queue lookup if it could not find the
    Destination in JNDI.  We need to ensure that we can support the old
    address model for backwards compatability.

----


> Core queue lookup with Artemis RA no longer works with 1x address model
> -----------------------------------------------------------------------
>
>                 Key: ARTEMIS-1658
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1658
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>            Reporter: Martyn Taylor
>            Priority: Major
>
> Artemis 1.x RA would do a core queue lookup if it could not find the
>  Destination in JNDI. We need to ensure that we can support the old
>  address model for backwards compatability.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to