Home/ Questions/Q 3215148
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-17T15:08:38+00:00

I have an application in C++, but it’ll need to ‘talk’ to Java based

  • 0

I have an application in C++, but it’ll need to ‘talk’ to Java based message-service. In the past we used WebSphere MQ and used their C++ libraries to do the ‘talking’.

So I am in search of (ideally) free C++ to Java solution which doesn’t hold the whole JVM in memory.

The other option I’ve looked into is SOAP.
I’ve looked into Axis2-C but it gives me the whole server implementation, which I don’t need.
I’ve seen talk about gSOAP but saw mixed comments here. And again it seems to be providing me with a whole server.

I could write the code myself – but it goes against my (Java based) belief that excellent free code exists out there.

Thanks!
A’z

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    There are a couple of points here which don’t make sense to me, JMS is a java specific abstraction over a generic messaging API, much the same way that JDBC is a java specific abstraction over a generic database API.
    I can’t imagine anyone wanting a JDBC driver for a C++ application, they would rather use an ODBC driver.

    So if I assume that your objective is to send messages without using Websphere MQ from a C++ application, then I can recommend that you consider the following:

    • Do you need asynchronous messaging? i.e. store message on queue until message is consumed?
    • If yes, then web-services will not work for your application, unless you are prepared to host a web-server to receive the responses, and call back to your application.

    You haven’t mentioned whether the underlying java based message service is going to be JMS or WebServices.
    You could consider using ActiveMQ as a messaging provider, it provides an implementation of the JMS API and also implements the STOMP protocol, which has client libraries for a number of languages including C++.

    You could leave open your decision for end-point protocols while you try out various options, by implementing an integration layer using something like Mule.
    You can quickly develop small integrations on Mule e.g. to accept a Message on ActiveMQ, and post it to a WebService and put the WebService response on a different ActiveMQ response queue. Or vice-versa, accept web-service call and post SOAP onto JMS queue, wait for JMS response and build SOAP response.

    There are many ESB-like frameworks which can facilitate these sort of integrations to various degrees :

    EDIT:
    Given the clarification I will refine my answer:

    1. You need a common message broker that is accessible to C++ and Java such as ActiveMQ.
    2. You need a small / lightweight integration layer such as some of those above to accept from ActiveMQ and forward to SonicMQ, and vice-versa.

    2.1 From what I know of Sonic, they have an ESB stack that should be able to do this instead of using one of the containers/frameworks mentioned above, but that will open up issues of integration ownership between you and the client.

    I found 3 links showing Sonic support for C and C++ :
    – http://www.sonicsoftware.com/products/docs/sonicmq_app_server_ds.pdf
    – http://www.sonicsoftware.com/developer/documentation/docs/sonicmq_c_v60.pdf
    – http://communities.progress.com/pcom/servlet/JiveServlet/download/10809-3-10161/cclients_readme_76.htm (dodgy mime type on this link)

    • 0