[
https://issues.apache.org/jira/browse/PROTON-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472673#comment-13472673
]
Rob Godfrey commented on PROTON-65:
-----------------------------------
I think it's more of a module/scoping question.
I completely agree that we should have a JMS <-> Message adapter, hosted within
Apache Qpid. The question is really about the scope of "Proton" as a
sub-component of Qpid I think. One thing that a lot of us a very keen to
ensure is that "Proton" is seen as a whole not as a whole load of independent
language specific modules (since treating each language independently has
caused us many issues in the past).
> 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
