Rob Godfrey commented on PROTON-65:

I agree that right now we haven't identified the right place. One of the things 
that I think needs to be urgently addressed is defining the scope of what is 
"proton", how we structure to potentially accept intergations of proton, and 
where we place other code that utilises proton but is non-core.

I know some people are supposed to be writing a "constitution" for Proton at 
the moment... hopefully over the next week or so we can get agreement on this 
and find an agreed home for code such ass this.
> Provide a AMQP 1.0 Message to JMS Message mapping logic/module
> --------------------------------------------------------------
>                 Key: PROTON-65
>                 URL: https://issues.apache.org/jira/browse/PROTON-65
>             Project: Qpid Proton
>          Issue Type: New Feature
>          Components: proton-j
>            Reporter: Hiram Chirino
>         Attachments: PROTON-65.patch
> Having a easy/consistent way to transform a JMS message to an AMQP message 
> and back would be super handy.  Having that logic live in proton would help 
> make that mapping more standardized as different client and sever 
> implementations can just re-use the logic.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to