Call NodeJs package generic static method in NodeJs package app

This article provides an introduction to cross-technology invocation of static generic methods. Generic methods in C# (.NET) and Java technologies are methods that are declared with the type parameter in its signature, allowing it to be used with any data type. It is described in detail in article about generic methods in .NET and article about generic methods in Java.

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.

With Javonet you can interact with generic static methods from NodeJs package like they were available in any language but invocation must be performed through Javonet SDK API.

Javonet allows you to pass any any language value type as argument to method from NodeJs package. For reference type arguments (instances of other classes) you can create such instance with Javonet and pass the Invocation Context variable referencing that object as argument of method invocation.

Custom NodeJs package with generic static methods

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

Snippet below represents the sample code from NodeJs package which contains generic methods.

It is possible to invoke the methods from NodeJs package using following any language code:

This snippet uses in memory runtime bridging to load the NodeJs package and next retrieves reference to specific type.
Next, generic static method is invoked.
While calling .NET generic method it is necessary to pass method name, type and arguments.
While calling Java generic method it is necessary to pass method name and arguments.

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 NodeJs package 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.