Interesting Idea for the .NET-Java Bridge
Here's a nicer way to setup the Java side of JNBridge...
Proposal: The Maximo plugin, when it is started, could start up the Java side of the proxy. This would mean we wouldn't need to maintain a separate service that runs this side of the bridge.
The plugin could the monitor the proxy and restart it if needed.
An additional advantage, if we upgrade to JNBridge 2.1, would be that we can take advantage of the new in-process memory features of the bridge. With the new version, if the .NET and Java sides are on the same machine, should have performance gains from not needing any network transport between .NET and Java (the RMI connection would still go over the wire).
