http://qpid.apache.org/components/index.html#compatibility
I updated that table and made an attempt to clarify what aspect is relevant
for compatible communication.
On Tue, Feb 16, 2016 at 2:04 PM, Robbie Gemmell
wrote:
> As steve mentions the language the broker is written in matters not,
> th
As steve mentions the language the broker is written in matters not,
they speak AMQP and clients can do the same in whatever language they
like which is one reason client language isn't overly mentioned in
docs.
The examples that ship with both the AMQP 1.0 and AMQP 0-x JMS clients
work against th
Steve,
Exactly what I needed! Thank you!
If we ever meet the first round is on me!
Paul
From: Steve Huston [shus...@riverace.com]
Sent: Tuesday, February 16, 2016 3:34 PM
To: users@qpid.apache.org
Subject: RE: QPID C++ broker and Java - One broker to "
Hi Paul,
> -Original Message-
> From: Flores, Paul A. [mailto:paul.a.flo...@saic.com]
> Sent: Tuesday, February 16, 2016 4:26 PM
> To: users@qpid.apache.org
> Subject: RE: QPID C++ broker and Java - One broker to "rule them all"
>
> Steve,
>
> The compatibility table is what drew me to p
Steve,
The compatibility table is what drew me to posting my original question.
We are using the QPID Messaging API which notable does not list Java language
support.
Brokers appear to be language dependent implementations. In passing the C++
Broker documentation mentions in a one liner tha
There's a compatibility matrix on the page:
http://qpid.apache.org/components/index.html
If that doesn't contain all the info you need to help decide, try asking again
- I may not understand the problem.
-Steve
> -Original Message-
> From: Flores, Paul A. [mailto:paul.a.flo...@saic.com]
+1
* Checked signatures and checksums
* Built the source bundle and ran the tests
* Ran the included example against an ActiveMQ broker
* Tested the ActiveMQ broker AMQP module using the staged artifacts
* Reviewed the license and notice files in both the src and bin archives
On 02/16/2016 12:15
Per Steve's advice:
Environment:
Centos 5.11 (moving soon to 7)
C++: gcc 4.1.2
Java: 1.7.0_95
QPID Messaging API: qpid-cpp-0.34
C++ Broker
From: Steve Huston [shus...@riverace.com]
Sent: Tuesday, February 16, 2016 12:13 PM
To: users@qpid.apache.org
Subject
As long as the front end, back end, and broker can speak the same AMQP version,
they should all play nice regardless of the programming language.
If you can be a little more specific about the client code versions, it's
highly likely that someone can help point you to at least one broker to do t
Situation:
I am looking at a mixed language implementation.
Server side (backend) is in C++ while user facing side (frontend) is Java.
A fair amount of JNI "in play".
Specific option of using JMS would be painful because there is a substantial
amount of backend communications between s
Hi folks,
I have put together a spin for a 0.8.0 Qpid JMS client release, please
test it and vote accordingly.
The source and binary archives can be grabbed from here:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.8.0-rc1/
Those files and the other maven artifacts are also staged for now at:
The Apache Qpid community is pleased to announce the immediate
availability of Apache Qpid Proton 0.12.0.
Qpid Proton is an AMQP 1.0 messaging library. It can be used in a wide
range of messaging applications including brokers, clients, routers,
bridges, proxies, and more.
This release incorporat
12 matches
Mail list logo
