[
https://issues.apache.org/jira/browse/PROTON-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472540#comment-13472540
]
Rajith Attapattu commented on PROTON-65:
----------------------------------------
Hiram,
First of all, thx for confirming that it's indeed a separate jar. I figured it
was the case, but wasn't too sure given that I haven't messed with mvn for long.
I certainly see the value of having a mapping btw the AMQP message <---> JMS
Message and make it available for other folks to use it.
But I'm not sure if proton is the right place to have it.
Now to be fair to you, this is a discussion that goes beyond this particular
issue.
We have to make a clear statement about what proton is and what proton is not.
Based on the discussions we had so far about the goals of proton, this doesn't
seem to fit in well.
IMO this is something that is best housed at Qpid (or even ActiveMQ for the
time being).
Again this is only my opinion. I would talk to other folks as well to see what
they think about this.
Regards,
Rajith
> 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
