[
https://issues.apache.org/jira/browse/QPIDJMS-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15063035#comment-15063035
]
Timothy Bish commented on QPIDJMS-143:
--------------------------------------
Thanks for popping that answer in here Rob, was hoping that when this question
hit the mailing list (looks like is has now) you'd offer some history on the
older JMS client bits. :)
> What Qpid AMQP 1.0 client to use?
> ---------------------------------
>
> Key: QPIDJMS-143
> URL: https://issues.apache.org/jira/browse/QPIDJMS-143
> Project: Qpid JMS
> Issue Type: Task
> Components: qpid-jms-client
> Affects Versions: 0.6.0
> Reporter: Mark Soderquist
>
> Over the months I have found at least four Qpid client libraries that could
> be used to implement a Java AMQP 1.0 client. My challenge is knowing what I
> should use. I'm not sure what clients will be supported and some of them I
> have yet to get to work. I will list the libraries by their Maven artifact id:
> qpid-jms-client: Found easily on the Qpid web site. I have been able to send,
> but not receive messages.
> proton-j: Looks great. API looks simple. I have never been able to send or
> receive messages.
> qpid-amqp-1-0-client: This is the library I have used for non-JMS
> implementations. I have been able to both send and receive messages. It
> performs well but appears to not be supported after version 0.32.
> qpid-amqp-1-0-client-jms: This is the library I have used for JMS
> implementations. I have been able to both send and receive messages. It
> performs well but appears to not be supported after version 0.32.
> I'm just trying to understand what works today and what direction Qpid client
> development is going. I don't want to be using something that doesn't work
> but I also don't want to use something that is deprecated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
