On Mon, 17 Apr 2000 12:42:32 +0200, [EMAIL PROTECTED] wrote:
>Hi,
>
>IMO the problem with J-Integra is, that there is no direct COM-CORBA
>communication. You always have a Java-Layer with its VM on the client.
You don't need a JVM on the Windows client machine which talks to an EJB.
[Java Object<--jintegra.jar]<--dcom<--[COM client]
To answer Martin's question, J-Integra allows DCOM calls onto Java objects
(the runtime receives a DCOM requests, unmarshalls parameters and invokes a
method on a target Java object). That target Java object could in fact be a
CORBA stub, an RMI stub, or a real Java object. In some cases it is
possible to load J-Integra into the App Server's JVM so as to skip the RMI
step when invoking methods on EJBs. It supports both early-bound (vtable)
and late-bound (IDispatch) invocations -- the COM client sees a COM object.
(It also allows calls onto COM objects from Java clients, would could be
EJBs, etc.).
Full doc http://www.linar.com/jintegra/doc/
--
Damian Mehers.
Linar Ltd. +44 (0)7050 669643 http://www.linar.com/
J-Integra - the world's only pure Java-COM bridge
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
