Invoke static methods

This article provides an introduction to cross-technology invocation of static methods.

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 static methods from .NET DLL like they were available in Ruby but invocation must be performed through Javonet SDK API, passing the name of the target method as String.

Javonet allows you to pass any Ruby value type as argument to static method from .NET DLL. In example: int, float, string, char, long and other. 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 static method invocation.

Call static method from custom .NET DLL

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

Snippet below represents the sample code from .NET DLL which contains class and its methods:

namespace TestClass
{
	public class TestClass
	{
		public TestClass() { }

        public static int MultiplyByTwo(int a)
        {
        	return 2 * a;
        }
        
        public int MultiplyTwoNumbers(int a, int b)
        {
        	return a * b;
        }
	}
}
public static int MultiplyByTwo(int a)
{
	return 2 * a;
}

public int MultiplyTwoNumbers(int a, int b)
{
	return a * b;
}

It is possible to invoke one of the declared static methods from .NET DLL using following Ruby code.

require 'javonet-ruby-sdk'

resources_directory = "."

# use activate only once in your app
Javonet.activate('your-license-key')

# create called runtime context
called_runtime = Javonet.in_memory.netcore

# set up variables
library_path = "#{resources_directory}/TestClass.dll"
class_name = 'TestClass.TestClass'

# load custom library
called_runtime.load_library(library_path)

# get type from the runtime
called_runtime_type = called_runtime.get_type(class_name).execute

# invoke type's static method
response = called_runtime_type.invoke_static_method('MultiplyByTwo', 25).execute

# get value from response
result = response.get_value

# write result to console
puts result
namespace TestClass
{
	public class TestClass
	{
		public TestClass() { }

        public static int MultiplyByTwo(int a)
        {
        	return 2 * a;
        }
        
        public int MultiplyTwoNumbers(int a, int b)
        {
        	return a * b;
        }
	}
}
# use activate only once in your app
Javonet.activate('your-license-key')

# create called runtime context
called_runtime = Javonet.in_memory.netcore

# set up variables
library_path = "#{resources_directory}/TestClass.dll"
class_name = 'TestClass.TestClass'

# load custom library
called_runtime.load_library(library_path)

# get type from the runtime
called_runtime_type = called_runtime.get_type(class_name).execute

# invoke type's static method
response = called_runtime_type.invoke_static_method('MultiplyByTwo', 25).execute

# get value from response
result = response.get_value

# write result to console
puts result

In code snippet above you can see how easily you can activate Javonet and instruct it using inMemory() method to create new RuntimeContext that will run net-dll runtime within your current process. Next with addLibrary method it triggers the load of required net-dll module and allows you to interact with any classes and their static methods defined in that package.

Further calls to invokeStaticMethod() allows to call "multiplyByTwo" net-dll static method and pass the value type arguments. With Javonet you can invoke methods with any number and any type of arguments including value type arguments, reference type arguments, arrays and collections.

You can receive and further process and type of result returned by called net-dll method, regardless if it is reference type that will get returned as another instance of Invocation Context that you can use for further interaction, or value type that you can obtain as ruby value with getValue() method.

Call static methods from standard .NET DLL

With Javonet you can interact not only with any custom net-dll module but also with any net-dll framework objects. The same steps are required to use types and methods from standard .NET DLL framework class:

require 'javonet-ruby-sdk'

resources_directory = "."

# use activate only once in your app
Javonet.activate('your-license-key')

# create called runtime context
called_runtime = Javonet.in_memory.netcore

# get type from the runtime
called_runtime_type = called_runtime.get_type('System.Math').execute

# invoke type's static method
response = called_runtime_type.invoke_static_method('Abs', -50).execute

# get value from response
result = response.get_value

# write result to console
puts result
namespace TestClass
{
	public class TestClass
	{
		public TestClass() { }

        // empty
	}
}
# use activate only once in your app
Javonet.activate('your-license-key')

# create called runtime context
called_runtime = Javonet.in_memory.netcore

# get type from the runtime
called_runtime_type = called_runtime.get_type('System.Math').execute

# invoke type's static method
response = called_runtime_type.invoke_static_method('Abs', -50).execute

# get value from response
result = response.get_value

# write result to console
puts result

In sample above you see how the Javonet allows to create an instance of .NET DLL Math class and interact with its static abs method. 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 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.