You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by JonathanMalek <gi...@git.apache.org> on 2016/06/05 00:00:56 UTC

[GitHub] activemq pull request #188: AMQ-6310 added a check to ensure the leading wil...

GitHub user JonathanMalek opened a pull request:

    https://github.com/apache/activemq/pull/188

    AMQ-6310 added a check to ensure the leading wildcards in prefixes are handled correctly.

    Checking for leading wildcard in the prefix for a virtualtopic, modifying the behavior of shouldDispatch in the VirtualTopicInterceptor.

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

    $ git pull https://github.com/JonathanMalek/activemq master

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

    https://github.com/apache/activemq/pull/188.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 #188
    
----
commit 6bf5987921f6fdb6844652bb77e2fc14b002ccf2
Author: Jonathan Malek <jo...@jonathanmalek.me>
Date:   2016-06-04T23:51:27Z

    A fix for AMQ-6310
    
    Checking for leading wildcard in the prefix for a virtualtopic,
    modifying the behavior of shouldDispatch in the VirtualTopicInterceptor.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] activemq pull request #188: AMQ-6310 added a check to ensure the leading wil...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/activemq/pull/188


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---