| <div class="wiki-content maincontent"><p>It is very common for an organisation to have lots of legacy C code which needs integration into the message bus. The current available solutions are</p> |
| <ul><li><a shape="rect" class="unresolved" href="#">CMS</a> is an easy-to-use JMS 1.1-like API for C++. Our implementation of CMS is called ActiveMQ-CPP, the architecture for which supports pluggable transport protocols, very much like the ActiveMQ broker itself.</li><li>use the <a shape="rect" href="openwire-c-client.xml">OpenWire C Client</a> which is only available in ActiveMQ 4.x or later.</li><li>we are working on the <a shape="rect" href="openwire-cpp-client.xml">OpenWire CPP Client</a></li></ul> |
| |
| |
| <ul><li>use the <a shape="rect" class="external-link" href="http://stomp.codehaus.org/C" rel="nofollow">Stomp C Client</a> for any version of ActiveMQ from 3.1 onwards. You can also use <a shape="rect" class="external-link" href="http://stomp.codehaus.org/" rel="nofollow">Stomp</a> from many other languages like .Net, Python, Ruby, Perl etc.</li></ul> |
| |
| |
| <p>Other alternative mechanisms to communicate using.</p> |
| <ul><li>use the <a shape="rect" href="rest.xml">REST</a> API</li><li>use <a shape="rect" class="external-link" href="http://servicemix.org/WS+Notification" rel="nofollow">WS-Notification</a> and generate C bindings to WS-Notification using a SOAP stack</li><li>use <a shape="rect" href="how-do-i-access-activemq-from-csharp-or-dotnet.xml">.Net or Mono</a> to use ActiveMQ insided .Net</li><li><a shape="rect" href="compile-activemq-with-gcj.xml">Compile ActiveMQ with GCJ</a> to get a native C/C++ library</li><li>link to the ActiveMQ Java client using JNI</li><li>Use a Jabber client to talk to the ActiveMQ broker via the <a shape="rect" href="xmpp.xml">XMPP</a> protocol</li></ul></div> |
| |
