Work with JAR library exceptions in JavaScript app

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 JavaScript 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 JAR library with exception handling

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

Snippet below represents the sample code from JAR library which contains a chain of methods:

import java.util.*;
import java.lang.*;

public class TestClass {
    public TestClass() { }

        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;
        }
}
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 JavaScript:

const { Javonet } = require('javonet-nodejs-sdk/lib/sdk/Javonet')

let resourcesDirectory = '.'

// use Activate only once in your app
Javonet.activate("your-license-key")

// create called runtime context
let calledRuntime = Javonet.inMemory().jvm()

// set up variables
const libraryPath = resourcesDirectory + '/TestClass.jar'
const className = 'TestClass'

// load custom library
calledRuntime.loadLibrary(libraryPath)

// get type from the runtime
let calledRuntimeType = calledRuntime.getType(className).execute()

// invoke type's static method which throws exception
try {
    let response = calledRuntimeType.invokeStaticMethod("divideBy", 10, 0).execute()
} catch (e) {
    // write exception to console
    console.log(e)
    return
}
import java.util.*;
import java.lang.*;

public class TestClass {
    public TestClass() { }

        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;
        }
}
// use Activate only once in your app
Javonet.activate("your-license-key")

// create called runtime context
let calledRuntime = Javonet.inMemory().jvm()

// set up variables
const libraryPath = resourcesDirectory + '/TestClass.jar'
const className = 'TestClass'

// load custom library
calledRuntime.loadLibrary(libraryPath)

// get type from the runtime
let calledRuntimeType = calledRuntime.getType(className).execute()

// invoke type's static method which throws exception
try {
    let response = calledRuntimeType.invokeStaticMethod("divideBy", 10, 0).execute()
} catch (e) {
    // write exception to console
    console.log(e)
    return
}

The last method throws exception which is handled and rethrown in JavaScript. 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 JAR library 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.