Release notes

Ver 2.2.1.200603

  • Removed the limitation to a single embeddable instance if the JavaUI control has its own message pump detached from main UI message pump
  • Removed limitation on JCRefOut to single object: management of arrays now is a public feature
  • Exposed internal API, on both JCType and JCObject, to interact with underlying System.Type and fields
  • Solved minor issues

Ver 2.2.0.200516

This update adds new wrapper libraries for Windows and Linux. News in this update:

  • On platforms, where WindowsDesktop is supported, it is possible to integrate a Java Component within the WPF/WindowsForm main application
  • Added new Java event management (Mouse, Keyboard, Focus, etc) to help users with ready made classes
  • Now shared objects between CLR and JVM are available on .NET Core
  • Added win-arm, win-arm64, linux-arm and linux-arm64 wrapper libraries
  • Runtime Identifier is no more mandatory, Java Initialize does not needs it from the command line; if it is not found automatically the user must specify it
  • Added functions to start external thread and daemon thread from .NET
  • Minor change on API and interfaces to better cover some behaviors
  • Solved minor issues

Known limitations:

  • .NET Core Type identification from Java code needs, in some condition, an explicit assembly qualified name. Some types reported to be in one assembly really is managed from another one: e.g. System.Uri, System.Runtime.dll (https://docs.microsoft.com/it-it/dotnet/api/system.uri?view=netcore-3.1) really is managed from System.Private.Uri.dll

Ver 2.1.0.200415

This update introduces the general availability to invoke .NET Core API from Java. With this update both .NET Core and .NET Framework are aligned with a complete bidirectional communication between JVM and CLR. News in this update:

  • New command line switch available for Java

Known limitations:

  • The NET Core initialization libraries are available for Windows x86/x64 and Linux x64. Other platforms available on demand.
  • .NET Core Type identification from Java code needs an explicit assembly qualified name: it will be updated in a future release; .NET Framework has a better type resolver.
  • WindowsDesktop is an experimental feature. Do not use it in production: use the version available on https://www.jcobridge.com instead.

Ver 2.0.1.200409

This is critical patch update to solve an issue revealed in version 2.0.0.200321. The previous version will be retired.
Other news in this update

  • Added missing J2CBridge wrapping libraries for Linux x86/x64
  • New command line switch for license search path
  • Simplified usage of SetupJVMWrapper initialization class

Ver 2.0.0.200321

The major improvements of this version is on the CLR host: now it is possible to use .NET Core on different operating system.

JVM (Available only for .NET Framework, .NET Core coming soon)

  • Added event management for JVM graphical environment (AWT/Swing)
  • All features of previous versions

CLR (Available for .NET Framework on Windows and .NET Core on Windows and Linux, other platforms available on demand)

  • Added .NET Core host (Windows/Linux), other platfoms are available on demand
  • Management of events coming from JVM graphical environment
  • All features of previous versions

Ver 1.0.2.0

  • minor fix
  • minor performance improvement

Ver 1.0.0.0

JVM

  • Retrieve CLR Type
  • Instantiate CLR object
  • Invoke static or instance methods
  • Get or set static or instance properties
  • Subscribe to events
  • Integrates into AWT or Swing both WPF and WinForms controls, managing properties and events

CLR

  • Retrieve JVM class
  • Instantiate JVM objects
  • Invoke static or instance methods
  • Get or set static or instance fields
  • Use dynamic access to write code in a seamless way as it is done in Java language
  • Use specific interface to direct manages methods and fields