Exceptions from .NET Framework DLL in Java

This article provides an introduction to cross-technology handling of exceptions. Exceptions in programming are events that occur during the execution of programs that disrupt the normal flow of instructions.

Any exception thrown by called technology is handled and thrown as any other exception in Java code. Details of exception depend on called technology, but in most cases final exception has all the information passed by called side.

Javonet allows you to reference and use modules or packages written in (Java/Kotlin/Groovy/Clojure, C#/VB.NET, Ruby, Perl, Python, JavaScript/TypeScript) like they were created in your technology. If have not yet created your first project check Javonet overview and quick start guides for your technology.

Custom .NET Framework DLL withe exception handling in Java

With Javonet it is possible to reference any custom .NET Framework DLL and interact with its methods declared on types defined within that module almost the same as with any other Java library.

Snippet below represents the sample code from .NET Framework DLL which contains a chain of methods:

public static int DivideBy(int x, int y)
	return DivideBySecond(x, y);

public static int DivideBySecond(int x, int y)
	return DivideByThird(x, y);

public static int DivideByThird(int x, int y)
	return x / y;

To invoke these methods in Java:

// use activate only once in your app

// create called runtime context
RuntimeContext calledRuntime = Javonet.inMemory().clr();

// set up variables
String libraryPath = resourcesDirectory + "/TestClass.dll";
String className = "TestClass.TestClass";

// load custom library

// get type from runtime
InvocationContext calledRuntimeType = calledRuntime.getType(className).execute();

// invoke type's static method which throws exception
try {
    calledRuntimeType.invokeStaticMethod("DivideBy", 10, 0).execute();
catch (Exception ex) {
    // write exception message to console

The last method throws exception which is handled and rethrown in Java. Then the exception in catched and printed.

The same operation can be performed remotely by just changing the new Runtime Context invocation from in memory to tcp that will create and interact with your .NET Framework DLL objects on any remote node, container or service that hosts Javonet Code Gateway. This way you can preserve the same logic in your application and instantly switch between monolithic and microservices architecture without the need to implement the integration layer based on web services or other remote invocation methods.

Read more about use cases and software architecture scenarios where Javonet runtime bridging technology can support your development process.