Javonet is the native integration technology that allows for the seamless integration between Java and .NET and it has the certain advantages over the alternative approaches of integrating Java and .NET. We have covered them in our previous posts:
Compared to the alternatives like Web services or the custom native wrappers Javonet implementation results in much less development and therefore less deployment artifacts. This in practice means that there are much less code elements and parts to be bug fixed, maintained or supported.
At the same time the deployment of the ready solution that uses Javonet to make Java and .NET speak to each other easily is much easier and much less time and cost consuming. The transitions between the development environments (Developement, Test and Production) becomes much more comfortable, easier and safer.
This is possible not only because there are much less additional “elements” required to accomplish the robust integration but also the Java JARs and Javonet DLLs can be embedded as a part of single Java or .NET application artifact regardless of the type of the project (web, desktop, or service).
Below we have made a comparison of the deployment artifacts that are related to the alternative ways of integrating Java and .NET and to the integration done with Javonet.