: junc++ion use case

Publish a C++ Version of Your Java API

In the previous use cases we talked about leveraging Java code in your C++ application, but many of our customers are actually developing products in Java. They have decided that offering a C++ integration API for their product gives them a competitive advantage.

Using JunC++ion, our customers generate C++ proxy types for their product and then usually ship the header files and a set of libraries for their customers to use. The C++ developers compile against the supplied header files and link with the supplied libraries.

Now, to be fair, this approach is not for everyone. If you wish to have a pure C++ solution and you cannot have Java be a part of your solution, then this is not for you because at runtime the integrated product still requires a JVM and the Java types for which the C++ proxies were generated.

Some vendors, mostly those with a product that performs a communication service over sockets, can provide a pure C++ API for their product because at its heart is a wire protocol and not a Java type. Their Java APIs are often themselves just a bridge to the underlying protocol. This is not the general case.

If you publish a Java product with a sizable API that your customers use, you can take any one of several approaches with respect to C++:

Which path is right for you depends on a lot of factors but we recommend that you make an educated choice and don't just ignore the question.