[
https://issues.apache.org/jira/browse/PROTON-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472449#comment-13472449
]
Rajith Attapattu commented on PROTON-65:
----------------------------------------
Hiram,
One of the goals of proton is to be as as dependency free as possible, so it
can be used in as many environments as possible.
>From that pov I don't think this is a good idea at all.
For example, having the jms library as a dependency will be a big issue in
using proton-j in Android (or similar environments).
On the other hand if we can make this as a separate optional jar (maybe thats
what you are doing in this patch, and I haven't messed with maven for ages)
then that maybe acceptable.
But still I'm not too comfortable with the idea. I'm not too sure if proton is
the place to do so.
I would like to see comments from other interested parties 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
