Peter
On Mon, 2/29/16, artnaseef wrote:
Subject: Re: Recommendation for vendor independent strategy
To: users@activemq.apache.org
Date: Monday, February 29, 2016, 7:04 PM
It may be possible to
build a facade, if you don't need all of the features
of th
It may be possible to build a facade, if you don't need all of the features
of the 2.0 spec.
For example, ActiveMQ has an async send features that producers can use,
which may meet your needs.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Recommendation-for-v
Even then, JMS 2.0 is a client library. Its not the protocol
implementation to your backing queue. On the flip side, there are many
AMQP implementations, it may be a better approach to connecting in a vendor
agnostic way.
John
On Mon, Feb 29, 2016 at 8:39 PM Tim Bain wrote:
> I'm not aware of
I'm not aware of a plan to implement JMS 2.0 in ActiveMQ 5.x. I believe
Artemis implements JMS 2.0, but you'd have to convince your potential
customer to switch to it and it's not a simple drop-in replacement so they
might not be willing to do that just to use your "thingy."
I'm not aware of anyo
Hi there
We've developed a "thingy" that integrates with various messaging
architectures. So far - at the sites where we have deployed - we've had IBM MQ,
Tibco Message Service and even a Wildlfy installation (HornetQ) at the other
end. We've developed in Java and used JMS so we use exactly the
