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

ASF GitHub Bot commented on ACTIVEMQ6-89:
-----------------------------------------

GitHub user clebertsuconic opened a pull request:

    https://github.com/apache/activemq-6/pull/191

    ACTIVEMQ6-89  Interceptors on Stomp

    

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

    $ git pull https://github.com/clebertsuconic/activemq-6 mastanik

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

    https://github.com/apache/activemq-6/pull/191.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 #191
    
----
commit c796e37c9c097af7c03c3df8841e41d3e7b4117d
Author: nberdikov <nberdi...@groupon.com>
Date:   2015-03-13T09:29:33Z

    ACTIVEMQ6-89 Added possibility to intercept stomp frames
    
    https://issues.apache.org/jira/browse/ACTIVEMQ6-89
    
    This was originally contributed at #182. We have squashed the commits and 
rebased them here
    This closes #182

commit 63ad8eba128efd5e46401530c6dbf5b96fb8fcaf
Author: Clebert Suconic <clebertsuco...@apache.org>
Date:   2015-03-16T19:11:25Z

    ACTIVEMQ6-89 Refactored stomp support contributed
    
    https://issues.apache.org/jira/browse/ACTIVEMQ6-89
    
    I have done a lot of refactoring on this. So we can a different version of 
the interceptor for each protocol based on a base class now.
    Just an abstract class over Stomp would be a bit hacky... this is a better 
approach.

----


> Intercepting support for stomp
> ------------------------------
>
>                 Key: ACTIVEMQ6-89
>                 URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-89
>             Project: Apache ActiveMQ 6
>          Issue Type: New Feature
>    Affects Versions: 6.0.0
>            Reporter: clebert suconic
>            Assignee: clebert suconic
>             Fix For: 6.1.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to