Configuring the Runtime for .NET v3 Proxy Types Tutorial
The purpose of this tutorial is to introduce you to the basics of configuring .NET applications that use .NET v3 Proxy Types to access Java classes within an embedded Java Virtual Machine.
The v3 moniker stems from Codemesh's .NET runtime library that has to be compatible with
the proxy types because the proxy types delegate most of their work to that runtime library. The runtime
library is currently at major version 3, hence the v3 label.
A classic Java application usually requires a number of command line options to make sure that
When you execute Java code in a JVM that is embedded within a .NET application it stands to reason that you have to provide many of the same configuration settings for your Java code to execute properly. Additionally, you will probably want to specify the JVM that is to be used, as well as some options related to dealing with that JVM.
This tutorial is your guide to the JuggerNET Configuration API.
Prerequisites
We will use some of the examples that come bundled with your JuggerNET download. You should also have downloaded the runtime library for your platform and made sure that you have a C# compiler.
The lessons will still be useful as a reference, even if you don't have a C# compiler or the product installed.
Note: Links to runtime APIs embedded in tutoral lessons refer to the latest documented version of the runtime API.
Lesson Plan
| Lesson 1 |
Introduction Learn about the configuration API types and how they are used. |
| Lesson 2 |
Explicit Configuration Configure the runtime in code, usually from your program's |
| Lesson 3 |
File-based Configuration Configure the runtime with a configuration file. |
| Lesson 4 |
Configuration Hooks Embed configuration logic in a proxy assembly. |