MASES.JNet.Templates 1.5.2

JNet: .NET gateway for JVM APIs

JNet is a .NET gateway for JVM APIs (Java, Scala, Kotlin, ...) to use .NET and JVM side-by-side.

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.

Status

Latest status is:

Libraries

JNet	JNet.Templates	JNetPSCore<br>(version 1.4.9+)

Tools

JNetCLI<br>(version 1.4.8+)	JNetReflector<br>(version 1.4.8+)	JNetPS<br>(version 1.4.9+)

Pipelines

Scope of the project

This project aims to create a library to direct access, from .NET, all the features available in the Java Platform, this is the counterpart of JCOReflector.

There are many client libraries written to manage communication with Java. Conversely, this project use directly the Java packages giving more than one benefit:

• all implemented features are availables at no extra implementation costs, see JNet usage;
• avoids any third party communication protocol implementation;
• access all features made available from Java platform.

News

• V1.4.8+: From version 1.4.8 there is a new project, named JNetReflector (still in development phase), able to build C# gateway classes from JARs containing the JVM classes, exactly the same JCOReflector does for .NET in JVM.
• V1.4.9+: From version 1.4.9 there are two new projects:
  • JNetPSCore: the core library for PowerShell development, it can be extended in other projects based on JNet;
  • JNetPS: a PowerShell module to use JNet within a PowerShell shell.
• V1.5.2+: strong improvement of JNetReflector; it is used to generate almost all Java 11 classes available in the corresponding JNet version

Runtime engine

JNet 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 JVM;
  • JCOBridge does not use any other communication mechanism than JNI;
  • .NET (CLR) inherently inherits the cyber-security levels of running JVM;
• Direct access the JVM from any .NET application:
  • Any Java/Scala/Kotlin/... class can be directly managed;
  • No need to learn new APIs: we try to expose the same APIs in C# style;
  • No extra validation cycle on protocol and functionality: bug fix, improvements, new features are immediately available;
  • Documentation is shared;
• Dynamic code: it helps to write a Java/Scala/Kotlin/etc seamless language code directly inside a standard .NET application written in C#/VB.NET: look at this simple example and JNet APIs extensibility.

JCOBridge resources

Have a look at the following JCOBridge resources:

• Release notes
• Non Profit or University
• Commercial info: Professional or Enterprise
• Community Edition
• Commercial Edition
• Latest release:

Summary

• Roadmap
• Actual state
• JNet usage
• JNet APIs extensibility
• JNet CLI usage
• JNet Reflector usage
• JNet PowerShell usage