Doron Somer wrote:
> Chris,
>
> Could you provide some more details about your CORBA support. We have done
> internally something similar where users define components in CORBA IDL, and
> we use the tie approach + post processing of the _Operations interface to be
> a legitimate EJB/RMI remote interface.
>
> Do you know of other app servers that took this approach for providing CORBA
> interop.
For Sybase EAServer 3.5, we use CORBA 2.0 IDL to describe component
home & remote interfaces, with a proprietary extension to IDL that
we use for customers who insist on using Java classes that do not map
nicely onto CORBA struct types. The IDL can be hand-coded, or reverse
engineered from the EJB home & remote interfaces. This provides immediate
access to EJBs from CORBA 2.0 clients (even non-Sybase CORBA clients).
> It seems like it'll take time until ORB vendors will support java2idl and
> interoperability will be realistic (it isn't great even today without object
> by value).
If I could find a group of individuals willing to work on an alternative non-OBV
IDL mapping for EJBs, I would be willing to drive the process. Then at least
we could have REAL interoperability well before the whole OBV mess settles down.
________________________________________________________________________________
Evan Ireland Sybase EA Server Engineering [EMAIL PROTECTED]
Wellington - New Zealand +64 4 934-5856
===========================================================================
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".
