|
Running the program is easy. Simply modify the application configuration file on each side so it specifies
our chosen communication mechanism and its associated parameters.
The shared-memory communications channel will automatically cause a .NET CLR to be created in the same process
as the Java application when the Java application starts, and the Java code will seamlessly and directly communicate
with the .NET code. If the .NET side is on a different machine from the Java side, or if more than one
Java program will be accessing the .NET code, we can start up the CLR separately, and configure the two
sides to communicate via a socket-based communications channel. In either case, the Java and .NET code
remain the same; only the configuration information is changed.
In this tcp/binary example, we start up the .NET side of the program. Then we run the Java application.
Calls to the .NET code will automatically be made, and the .NET-side console window will display logging
messages resulting from the calls from the Java side.
|
