1. Getting started
- 1.1. Installing Javonet
- 1.2. Activating Javonet
- 1.3. Adding References to .NET Libraries
- 1.4. XML Configuration File
- 1.5. Using the Javonet Fluent Interface
- 1.7. Introduction to Using .NET Back-end and UI Components in Java
2. Calling methods
- 2.1. Invoking Static Methods
- 2.2. Creating Instance and Calling Instance Methods
- 2.3. Calling Generic Methods
3. Working with .NET Objects
- 3.1. Creating Instance Of Generic Object
- 3.2. Extending the .NET Class in Java and Wrapping .NET Methods
4. Fields and Properties
- 4.1. Get/Set Values for Static Fields and Properties
- 4.2. Get/Set Values for Instance Fields and Properties
5. Methods Arguments
- 5.1. Passing Reference-Type Arguments
- 5.2. Passing Arguments by Reference with “ref” and “out” Keywords
- 5.3. Passing typeof(Type) as Method Argument
- 5.4. Calling Overloaded Method Passing Null Argument
6. Nested Types
8. Arrays and Collections
- 8.1. Arrays: Using Value-Type and Reference-Type Arrays
- 8.2. Working with .NET arrays and collections from Java with Javonet
9. Embeding UI controls
10. Referencing libraries
11. Off-line activation
12. Events and Delegates
13. Disposing and Garabage Collection
14. .NET Configuration Files (AppConfig, WebConfig)
15. Exceptions, Debugging and Testing
- 15.. Handling Activation Issues
- 15.1. Handling .NET Exceptions
- 15.2. How to debug .NET code called from Java
- 15.3. Debugging Javonet Enabled Application
16. Strongly-Typed Wrappers
17. Advanced Activation and Licensing
- 17.1. Runtime vs. Offline vs. Compile Time Activation
- 17.2. Project Activation Tool
- 17.6. Delegating Activation Server
18 Other usage scenarios
This article explains the difference between offline activation, standard runtime activation and optional compile time activation. Javonet supports 3 types of activation to satisfy different distribution scenarios. Read further sections to understand which approach would be most appropriate for your project.
Runtime activation is the default option. It means that Javonet module will contact our activation server to retrieve the license during the first execution of an application that uses Javonet on the new machine. During the activation request the unique hardware ID of the machine that runs the application will be generated and sent to our servers including the license key and provided email address (either to Javonet.activate() method or through XML config file). Activation server validates the license key and checks if there are still any available slots for new machines for this key. If license is valid server will return the Javonet license in the XML format.
The license XML will be stored in “javonet.lic” file in the root directory of the application (or in the custom directory indicated in the configuration). License file stores signed approval to run Javonet on particular machine and depending on the conditions of your license it can include also the optional license limitations and license renewal date.
Offline activation works similarly to runtime activation. The only difference is that first the user generates the hardware ID of the target machine using our special tool “Javonet Stations Identity”, and then manually enters the hardware ID, license key and email address to the offline activation web form input fields. By submitting the form the user will receive the downloadable “javonet.lic” file which should subsequently be copied to root directory of the application or custom directory created for storing the license that shall be indicated in the configuration.
Javonet will verify the license file and approve or reject the usage of the product with each execution.
Compile Time Activation
Compile time activation is used for the per project activation or per project and hardware ID activation only. Therefore the compile activation way can be used only with Javonet Professional or Javonet Enterprise license. In this scenario Javonet license file is bound to particular Java modules that will be used through Javonet. In case of Javonet Professional license it is bound to both target modules and particular hardware IDs.
License file is generated during the compilation of the product by calling the “Javonet Project Activation Tool” at the end of the compilation process. Project activation tool connects to Javonet Activation Server and retrieves the license file. License file is stored in *.lic file. The name of the “*.lic” file will be displayed on the console after running the tool.
This license file should be included in any application package that uses Javonet and uploaded to the target machines. If the Javonet Professional is used, the separate “.lic” file will be created for each of the target machines. If the Javonet Enterprise license is used there will be a single license valid for all the machines.
Read more about Project Activation Tool.