Skip to content

A set of Java classes to use .NET from any JVM enabled language (Java, Kotlin, Scala and others)

License

Notifications You must be signed in to change notification settings

masesgroup/JCOReflector

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

572 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

JCOReflector (a .NET Java™ wrapper)

Java 8+ .NET 8+

JCOReflector is a comprehensive suite of libraries and tools to use Java™/JVM™ APIs (Java, Scala, Kotlin, ...) and .NET side-by-side.

Libraries and Tools

.NET Framework .NET 8 .NET 9 .NET 10
Maven Central Maven Central Maven Central Maven Central
JCOReflectorEngine JCOReflectorCLI
latest version downloads latest version downloads

Pipelines

CI_REFLECT_TEST_COMMIT CI_DOCS CI_MAVEN CI_RELEASE

Project disclaimer

JCOReflector is a project, curated by MASES Group, can be supported by the open-source community.

Its primary scope is to support other, public or internal, MASES Group projects: open-source community and commercial entities can use it for their needs and support this project, moreover there are dedicated community and commercial subscription plans.

The repository code and releases may contain bugs, the release cycle depends from critical discovered issues and/or enhancement requested from this or other projects.

Looking for the help of experts? MASES Group can help you design, build, deploy, and manage applications mixing .NET and JVM™ enabled languages.


The project

JCOReflectorEngine produces a set of .NET wrapper for Java™ as JARs that are available for download. It's simple to use: you only need to reference JCOReflector.jar in the class-path and use the .NET API within your Java™ projects like exposed in the example section.

The core of the project is the innovative JCOReflector, a reflection engine which automatically writes Java™ classes using .NET class reflection. JCOReflector can be used to reflects any .NET assembly (even assembly outside the Microsoft ones) into JARs. The generated wrapper classes are based on the powerful JCOBridge engine and extends its use to simplify the use of .NET from Java™(JVM™). It was created internally from us to support our customers, now we made it available for everyone.

This project adheres to the Contributor Covenant code of conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to coc_reporting@masesgroup.com.

Why JCOReflector?

Access .NET from Any Java Version (8 through 25)

JCOReflector enables Java applications—including legacy Java 8 systems—to call .NET libraries and frameworks directly:

// Java 8 application calling .NET
import system.Console;
import microsoft.ml.*;

public class LegacyApp {
    public static void main(String[] args) {
        // Call .NET ML.NET from Java 8!
        var mlContext = new MLContext();
        var prediction = model.predict(data);
        
        Console.WriteLine("Prediction: " + prediction);
    }
}

Key Benefits:

  • Java 8+ Compatible - Works with Java 8 through Java 25
  • No .NET Code Changes - Generated wrappers for any .NET assembly
  • Legacy Modernization - Add ML.NET, Azure SDKs to Java 8 apps
  • Gradual Migration - Keep Java 8, modernize capabilities

Use Case: Call modern .NET libraries (ML.NET, Azure SDK, etc.) from existing Java 8 applications without upgrading Java runtime.

Runtime engine

JCOReflector uses JCOBridge, and its features, to obtain many benefits:

  • Cyber-security:
    • JVM™ and CLR, or CoreCLR, runs in the same process, but are insulated from each other;
    • JCOBridge does not make any code injection into CLR or JVM™;
    • JCOBridge does not use any other communication mechanism than JNI;
    • JVM™ inherently inherits the cyber-security levels of running .NET (CLR);
  • Direct access the CLR from any JVM™ application:
    • No need to learn new APIs: we try to expose the same .NET APIs in Java™ style;
    • No extra validation cycle: bug fix, improvements, new features are immediately available;
    • Documentation is shared.

JCOBridge 2.6.* can be used for free without any obligations; you need to purchase a commercial license, or uninstall the software, if you have direct or indirect incomes from the product usage.

Supported Versions

Java:

  • ✅ Java 8 (JRE 1.8.0_161 or later)
  • ✅ Java 11 (LTS)
  • ✅ Java 17 (LTS)
  • ✅ Java 21 (LTS)
  • ✅ Java 25 (LTS)

Note: Works with Oracle JDK, OpenJDK, Amazon Corretto, Azul Zulu, and other compatible distributions.

.NET:

  • .NET Framework 4.6.2+
  • .NET 6, 8, 9, 10

Note for Java 8 Users: JCOReflector enables modernization of Java 8 applications by providing access to cutting-edge .NET libraries without requiring Java runtime upgrades. Oracle Extended Support for Java 8 runs until December 2030.

JCOBridge resources

Have a look at the following JCOBridge resources:

JCOBridge 2.5.* series 2.6.* series
JCOReflector > 1.12.* series > 1.16.* series
Release notes Link Link
Community Edition Conditions Conditions
Commercial Edition Information Information

Latest release: JCOBridge nuget

History of the project

This project started in 2019 with the aims to create a set of Java™ (JVM™) classes which mimic .NET (Framework/6/8) conterparts, in May 2020 the first commit in GitHub. Using this project it is possible to use .NET API in Java™ and all JVM™ enabled languages (Scala, Kotlin, and so on). The final output of JCOReflector are JARs. At its first stages no JARs was available: only the JCOBridge engine, the graphical UI that helps to manages reflection and the operations needed to finally build JARs was relased. Starting from recent relases automated continous integration and verification process are in places, so the produced JARs are directly available for download and is no more needed to manually rebuils JARs before use it. Anyway still possible to use JCOReflector to reflects any .NET assembly (even assembly outside the Microsoft ones) into JARs, and because JCOReflector uses templates it is not necessary to manually manages the output, special needs can be addressed dirctly inside the templates.

Simple example

package mscorlib;

import system.*;
import system.io.*;

public class HelloNET {
    public static void main(String[] args) {
        try {
            String filename = "test.txt";
            String result = "";
            if (File.Exists(filename)) {
                result = File.ReadAllText(filename);
				Console.WriteLine(result);
                result = result + "Java Execution ";
                File.WriteAllText(filename, result);
            }
            Console.WriteLine(result);
            Console.WriteLine("Exiting");
        } catch (FileNotFoundException fnfe) {
            fnfe.printStackTrace();
        } catch (Throwable tre) {
            tre.printStackTrace();
        }
        return;
    }
}

This is the result:

prompt> This is a text file for read/write operation
prompt> This is a text file for read/write operation Java Execution
prompt> Exiting

To run it runs a command like the following one:

java -cp JCOReflector.jar;. HelloNET

The full example code, and other ones, are in the project test folder.

A basic Scala examples is the following one:

package mscorlib

import system.Console
import system.Environment

object HelloIterator {
  def main(args: scala.Array[String]): Unit = {
    try {
      Environment.GetLogicalDrives.foreach(Console.WriteLine(_))
      Environment.Exit(0)
    } catch {
      case tre: Throwable =>
        tre.printStackTrace()
    }
  }
}

the same example written in Kotlin is the following one:

package mscorlib

import system.Console
import system.Environment

object HelloIterator {
    @JvmStatic
    fun main(args: Array<String>) {
        try {
            for (drive in Environment.GetLogicalDrives()) {
                Console.WriteLine(drive)
            }
            Environment.Exit(0)
        } catch (tre: Throwable) {
            tre.printStackTrace()
        }
    }
}

Whats in .NET for Java™?

From the point of view of .NET it is very simple to use Java™ classes and it is not necessary to have some kind of reflection classes:

  1. JCOBridge is able to access and execute directly within a JVM™ using C# code, from C# it is possible to execute directly Java™ code with a similar syntax: look at the examples in JCOBridge-Examples.
  2. The project JNet uses JCOBridge: a developer has some ready made Java™ classes to be used from .NET.

Current state

The JCOBridge is a mature platform for .NET assembly reflection, the .NET wrapper JARs are available and cover most of the .NET framework functionality.
The reflector executables, available for both Framework and CoreCLR, is limited in the following features:

Implemented in the reflector

  • Only public Types are available
  • Classes and public accessible methods
  • Interface
  • Enum: enumeration and flags are available
  • .NET exception are translated and thrown in code
  • Static classes are managed
  • Events
  • Arrays: partial support
  • Inheritance
  • Out/Ref parameters
  • Native types managed from JCOBridge are directly mapped to native Java™ type
  • Base types (System.Object, System.Type, System.Enum, System.Exception, System.Collections.ArrayList) are mapped to specific type into a support library (JCOReflector.jar)
  • Management of thrown declaration as expected in Java™: a generic Throwable is used with all exceptions found in code (used the algorithm in https://stackoverflow.com/questions/986180/how-can-i-determine-which-exceptions-can-be-thrown-by-a-given-method and code from https://docs.microsoft.com/en-us/archive/blogs/haibo_luo/)
  • Documentation

Not implemented in reflector:

  • Generic types
  • Method decoration (Attributes)
  • Unsafe methods
  • Fields

Limitations

C# and Java™ are different languages. The reflection process cannot reflects into Java™ some features available on C#: an example are properties where get/set is automatically choosed from C# compiler Other limitations comes from some differences between the two engines (CLR and JVM™). In all cases JCOBridge superside these limitations, but manual operations shall be made: do not change the reflected classes, override them in your code.

Java 8 Integration Use Cases

1. Machine Learning in Legacy Java

// Java 8 application using ML.NET
import microsoft.ml.*;
import microsoft.ml.data.*;

public class FraudDetection {
    public void detectFraud(Transaction transaction) {
        // ML.NET model trained in .NET
        MLContext mlContext = new MLContext();
        ITransformer model = mlContext.Model.Load("model.zip");
        
        // Predict from Java 8
        var prediction = model.Transform(transaction);
        
        if (prediction.isFraud()) {
            flagTransaction(transaction);
        }
    }
}

2. Azure Integration from Java 8

// Java 8 app using Azure .NET SDK
import com.azure.storage.blob.*;

public class DocumentProcessor {
    public void uploadToAzure(byte[] document) {
        // Azure Storage .NET SDK from Java 8
        BlobClient blobClient = new BlobClient(connectionString);
        blobClient.upload(document);
    }
}

3. Modern PDF Processing

// Java 8 using .NET PDF libraries
import itext7.*;

public class ReportGenerator {
    public void generateReport() {
        // Modern .NET PDF libraries from Java 8
        PdfWriter writer = new PdfWriter("report.pdf");
        // ... full .NET API available
    }
}

Migration Path:

Java 8 Legacy App
     ↓ JCOReflector
.NET Modern Libraries (ML.NET, Azure, etc.)
     ↓ Proven Value
Eventually migrate Java when ready

How to use the generator tool (JCOReflector)

In the root folder execute:

dotnet build JCOReflector\JCOReflector.sln

or

dotnet build JCOReflector\JCOReflectorCLI.sln

Within the folder bin you will find three subfolders:

  • net462 (available only on Windows platform)
  • net8.0 (available on .NET 8 supported platforms)
  • net9.0 (available on .NET 9 supported platforms)
  • net10.0 (available on .NET 10 supported platforms)

in each subfolder will be available two executables:

  • JCOReflectorCLI the CLI tool;
  • JCOReflectorGUI the GUI tool, below some screenshot:

JCOReflector JCOReflector

Reflected Assemblies

The folder src/jvm/src contains all reflected classes generated for .NET Framework (net462), 8 (net8.0), 9 (net9.0) and 10 (net10.0). Below the coverage statistics:

Statistics

.NET Framework .NET 8 .NET 9 .NET 10
FrameworkStatistic Net8Statistic Net9Statistic Net10Statistic