[GitHub] activemq-artemis pull request #580: ARTEMIS-568 Catch broken JMS selector ex...

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] activemq-artemis pull request #580: ARTEMIS-568 Catch broken JMS selector ex...

asfgit
GitHub user tabish121 opened a pull request:

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

    ARTEMIS-568 Catch broken JMS selector expressions

    Enforce an EOF on the expression so the selector parser keeps going and
    catches the broken selector statement.

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

    $ git pull https://github.com/tabish121/activemq-artemis ARTEMIS-568

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

    https://github.com/apache/activemq-artemis/pull/580.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 #580
   
----
commit 5c29cc9a28b8dde1937c29cd8cd06c2d9def70f8
Author: Timothy Bish <[hidden email]>
Date:   2016-06-14T23:05:27Z

    ARTEMIS-568 Catch broken JMS selector expressions
   
    Enforce an EOF on the expression so the selector parser keeps going and
    catches the broken selector statement.

----


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] activemq-artemis pull request #580: ARTEMIS-568 Catch broken JMS selector ex...

asfgit
Github user asfgit closed the pull request at:

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


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---