[omniORB] omniORB 3.0.x

[W. Eliot Kimber]

Daniel Popowich wrote:

> It works like this: you write your interface in java, implement your
> server in java and then run the rmic compiler with a special switch,
> as in: 'rmic -iiop -idl mydomain.Foo' and *poof* you end up with
> Foo.idl.  Now c++ or python programmers can compile Foo.idl and
> communicate with the java server.

So am I correct in understanding this to mean that, modulo the
non-support of valuetype, I don't have to explicitly write Java servants
(as I would in Python or C++) in order to give remote CORBA clients
access to the Java objects? If so, that's pretty handy.

However, it seems to me that in real applications, you will almost
always need to tailor your CORBA API in a way that is different from a
straight Java API (or a straight Python API for that matter), such that
a completely automatic mapping from Java classes to IDL classes will
usually not be the optimal solution. So maybe it's not such a big deal
in practice given that I may be motivated to write special Java CORBA
servants anyway?

Thanks,

E.

-- 
. . . . . . . . . . . . . . . . . . . . . . . .

W. Eliot Kimber | Lead Brain

1016 La Posada Dr. | Suite 240 | Austin TX  78752
    T 512.656.4139 |  F 512.419.1860 | eliot@isogen.com

w w w . d a t a c h a n n e l . c o m