On Tue, 2012-07-24 at 17:51 +0000, Alona Rossen wrote: 
> Yes, it absolutely helps. The last question - does JMS-like means that it 
> follow JMS standard?
> 

The API attempts to adhere to the standard as much is possible, given
there are language differences there are some places where things might
work a bit differently or we may add some additional things that are
nice to have which aren't part of the JMS API natively.  A browse
through the APIs in the CMS source should be helpful here.

> -----Original Message-----
> From: Timothy Bish [mailto:tabish...@gmail.com] 
> Sent: July 24, 2012 1:45 PM
> To: users@activemq.apache.org
> Subject: RE: CMS - is it a Java wrapper?
> 
> On Tue, 2012-07-24 at 16:21 +0000, Alona Rossen wrote: 
> > I will try to be more specific.
> > 
> > There is a commercial product which enables C++ or .NET applications to use 
> > any Java Message Service specification v1.0.2 or v1.1 -compliant JMS 
> > provider.
> > The functionality is based on generating C++ and .NET bindings for the JMS 
> > API and some assorted Java support types. Just to stress this fact: they 
> > generate bindings for Java types, they do not translate the Java types. 
> > This means that a JMS implementation is still required to perform the 
> > actual messaging, and the product simply provides an easy-to-use C++ and 
> > .NET gateway, both at development and run-time.
> > 
> > My question is if CMS also requires JMS implementation to perform actual 
> > messaging or it targets ActiveMQ message broker independently of Java.
> > 
> > Thank you, 
> > Alona
> 
> ActiveMQ-CPP requires no Java bindings, its a standalone C++ library
> that will work directly against ActiveMQ or it can communicate with a
> broker that implements the STOMP protocol.  There are a few required
> libraries that it needs to build, and OpenSSL is optional if you want
> SSL transport support. 
> 
> Hope that helps.  
> 
> 
> 
> > 
> > -----Original Message-----
> > From: Timothy Bish [mailto:tabish...@gmail.com] 
> > Sent: July 23, 2012 6:20 PM
> > To: users@activemq.apache.org
> > Subject: RE: CMS - is it a Java wrapper?
> > 
> > On Mon, 2012-07-23 at 19:42 +0000, Alona Rossen wrote: 
> > > Does it mean that it targets JMS functionality of ActiveMQ?
> > > 
> > 
> > Can you be a bit more specific?  The CMS client exposes a JMS like API
> > and has many of the same features as the ActiveMQ Java client such as
> > failover, message compression, etc.
> > 
> > > Thank you, 
> > > Alona
> > > 
> > > -----Original Message-----
> > > From: Timothy Bish [mailto:tabish...@gmail.com] 
> > > Sent: July-23-12 3:22 PM
> > > To: users@activemq.apache.org
> > > Subject: Re: CMS - is it a Java wrapper?
> > > 
> > > On Mon, 2012-07-23 at 19:14 +0000, Alona Rossen wrote: 
> > > > Hello,
> > > > 
> > > > Does CMS/ActiveMQ-CPP  target JMS? Is this a C++ wrapper for JMS API?
> > > > 
> > > > Thank you,
> > > > Alona
> > > > 
> > > > 
> > > 
> > > CMS is a JMS like API for C++ it supports communication with ActiveMQ
> > > via the native Openwire protocol or via Stomp messaging.  
> > > 
> > 
> 

-- 
Tim Bish
Sr Software Engineer | FuseSource Corp
tim.b...@fusesource.com | www.fusesource.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/

Reply via email to