The most obvious way, if you can also require the Java runtime engine and some
Java code to be deployed on the client systems is to write Java Bean wrappers
around the Java RMI stubs, then use an ActiveX wrapper for Java Beans to make
them available under VB.
Another way I can think of is if the Java server code uses CORBA for rmi
(which is pretty easy to do if I understand correctly), then you could use a
CORBA/COM bridge of some sort. This would not require and Java infrastructure
or code on the client.
I can think of some other ways, too. What about using SOAP, REST, or XML-RPC?
REST seems like a nice option because it's easy to implement write REST client
apps in other languages than VB or Java - such as Python.
>Hi,
>
[quoted text clipped - 18 lines]
>
>R.