: juggernet use case

Publish a .NET Version of Your Java API

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

Using JuggerNET, our customers generate .NET proxy types for their product and then usually an assembly for their customers to use. The .NET developers just add the supplied assembly and the JuggerNET runtime library to their application and they are good to go.

Now, to be fair, this approach is not for everyone. If you wish to have a pure .NET 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 .NET proxies were generated.

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 .NET:

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.