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

ASF GitHub Bot commented on PROTON-1410:
----------------------------------------

GitHub user clebertsuconic opened a pull request:

    https://github.com/apache/qpid-proton-j/pull/6

    PROTON-1410 Moving ThreadLocal logic for Decoders on Message to its own 
class

    I need to reuse the same Decoder used by the MessageImpl when creating my 
own special Message Type.
    
    https://issues.apache.org/jira/browse/PROTON-1410

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

    $ git pull https://github.com/clebertsuconic/qpid-proton-j proton-1410

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

    https://github.com/apache/qpid-proton-j/pull/6.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 #6
    
----
commit 32eff8b6fe8db32e13c4c95ef5fb72c5166bdd98
Author: Clebert Suconic <[email protected]>
Date:   2017-02-20T07:50:16Z

    PROTON-1410 Moving ThreadLocal logic for Decoders on Message to its own 
class
    
    I need to reuse the same Decoder used by the MessageImpl when creating my 
own special Message Type.
    
    https://issues.apache.org/jira/browse/PROTON-1410

----


> Move MessageImpl::TLS to an utility class
> -----------------------------------------
>
>                 Key: PROTON-1410
>                 URL: https://issues.apache.org/jira/browse/PROTON-1410
>             Project: Qpid Proton
>          Issue Type: Improvement
>            Reporter: clebert suconic
>
> I have a need to create a special Message on Artemis, that will only parse 
> the Header and send everything else as a byte array.
> Instead of duplicating the TLS logic, I would like to move this to its own 
> class so it could be reused.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to