Static Java fields and properties from .NET DLL

This article provides an introduction to cross-technology handling of static fields and properties.
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 field and properties from .NET DLL like they were available in Java but invocation must be performed through Javonet SDK API.

Get/Set static Java field from custom .NET DLL

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

Snippet below represents the sample code from .NET DLL which contains class with fields:

public int PublicValue { get; set; }
private int PrivateValue { get; }
public static int StaticValue = 3;

public TestClass(int publicValue, int privateValue)
{
	PublicValue = publicValue;
	PrivateValue = privateValue;
}

It is possible to get one of the declared static fields from .NET DLL using following Java code.

I code in:
// use activate only once in your app
Javonet.activate("your-license-key");

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

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

// load custom library
calledRuntime.loadLibrary(libraryPath);

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

// get type's static field
InvocationContext response = calledRuntimeType.getStaticField("StaticValue").execute();

// get value from response
int result = (int) response.getValue();

// write result to console
System.out.println(result);

This uses in memory runtime bridging to load the .NET DLL, and next retrieves reference to specific type and gets the static field. Result of the invocation is returned as regular Java value and can be used for further processing. It is possible to set one of the declared static fields from .NET DLL using following Java code.

I code in:
// use activate only once in your app
Javonet.activate("your-license-key");

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

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

// load custom library
calledRuntime.loadLibrary(libraryPath);

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

// set static field's value
calledRuntimeType.setStaticField("StaticValue", 75).execute();

// get type's static field
InvocationContext response = calledRuntimeType.getStaticField("StaticValue").execute();

// get value from response
int result = (int) response.getValue();

// write result to console
System.out.println(result);

This uses in memory runtime bridging to load the .NET DLL, and next retrieves reference to specific type, then sets and gets the static field. Result of the invocation is returned as regular Java value and can be used for further processing.

Get/Set static Java field from standard .NET DLL

The same steps are required to get types and fields from framework .NET DLL:

I code in:
// use activate only once in your app
Javonet.activate("your-license-key");

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

// get type from runtime
InvocationContext calledRuntimeType = calledRuntime.getType("System.Math").execute();

// invoke type's method
InvocationContext response = calledRuntimeType.getStaticField("PI").execute();

// get result from response
double result = (double) response.getValue();

// write result to console
System.out.println(result);

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.

Additional references