Yes, this is another reason why we had to support it. For example the
network management forum is defining a standard trouble ticket IDL.
> -----Original Message-----
> From: David Forslund [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 05, 1999 11:17 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: IDL from EJB
>
>
> I think there is a "standard" way to use IDL with EJB. It might be
> considered legacy, but interface standards are being created
> for vertical
> markets in healthcare, manufacturing, finance, etc. These
> standards are
> written in the language
> neutral IDL so that they can talk with a variety of systems.
> In this case,
> it is desirable to just "feed" the IDL to
> an EJB server and have it generate all the appropriate code,
> etc. to manage
> the distributed objects. In this case it
> is best not to start with the Java but with the IDL specification.
>
>
> At 09:31 AM 10/5/99 -0700, Doron Somer wrote:
> >It is. We had to do it to support legacy IDL interfaces that
> can not be
> >reverse engineered using standard java2idl.
> >
> > > -----Original Message-----
> > > From: A mailing list for Enterprise JavaBeans development
> > > [mailto:[EMAIL PROTECTED]]On Behalf Of Chris Raber
> > > Sent: Tuesday, October 05, 1999 8:10 AM
> > > To: [EMAIL PROTECTED]
> > > Subject: Re: IDL from EJB
> > >
> > >
> > > This is sort of the inverse approach that we took.
> > >
> > > We use Java interfaces to describe EJB Homes and Remotes,
> > > since this is what
> > > is prescribed by the specification. We map this to iiop under
> > > the hood.
> > >
> > > I am curious how customers feel about the CORBA centric
> > > approach to defining
> > > EJB interfaces? It feels rather non-stanard to me.
> > >
> > > -Chris.
> > >
> > > > -----Original Message-----
> > > > From: Evan Ireland [SMTP:[EMAIL PROTECTED]]
> > > > Sent: Monday, October 04, 1999 10:07 PM
> > > > To: [EMAIL PROTECTED]
> > > > Subject: Re: IDL from EJB
> > > >
> > > > 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".
> > >
> > > ==============================================================
> > > =============
> > > 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".
> > >
> >
> >=============================================================
> ==============
> >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".
>
> David W. Forslund [EMAIL PROTECTED]
> Advanced Computing
> Laboratory
> <http://www.acl.lanl.gov/> ~dwf>http://www.acl.lanl.gov/~dwf
>
> Los Alamos National
> Laboratory Los Alamos, NM 87545
> 505-665-1907 FAX: 505-665-4939
>
===========================================================================
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".
