Hi John,
Having done CORBA after EJB I found lots of similarities in both approaches.
Interesting that some CORBA vendors have built EJB
Appservers using their original CORBA ORBs.
CORBA buys you Cross-language capabilities, which I believe is the big
reason to use it. If I want to build an application with significant C++
code (Or a host of other languages) then CORBA provides a nice way to get
them all to talk. Problems do occur in mapping - especially between OO and
procedural languages. But that's not insurmountable. There are otherways
to get the cross-language thing... JNI for C++, or the RMI-COM bridge, SOAP.
But if there is a ORB available CORBA might be the easiest.
CORBA used to be a more robust solution due to its maturity.. but EJB
Application Servers are getting pretty robust these days.
CORBA is more of a pain to develop for. EJB is simplier and provides
protection around potential probs. For example, EJB never allows you to
talk to the actual backend object - construction is always through the home
object interface. CORBA has factories but you can mess with the resulting
object. In that way its more like RMI than EJB. There is of course the
extra step of writting to IDL rather than a language.. of course with Java
you can now usually build the IDL directly from the Java code.
CORBA gives you lots of flexibility and pluggability for management of
objects.. In fact, some App Servers have used a similar method to build
pluggable features into the server.
Of course you mentioned the big one... the infrastructure is already CORBA
based.
My own feeling is that, given a new development in Java with a need for
distributed objects, I'd go with EJB most times.
Hope this helps,
Jon
>From: John Harby <[EMAIL PROTECTED]>
>Reply-To: John Harby <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Guidelines on using CORBA in J2EE apps
>Date: Wed, 8 Aug 2001 16:06:03 +0000
>
>Does anyone know of some guidelines on when to use CORBA in J2EE apps? (I
>mean the application using an ORB and some CORBA objects itself, not the
>underlying app server). I can see this might be required if your app is
>interfacing with some native CORBA-based app, but when else?
>
>_________________________________________________________________
>Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
>
>===========================================================================
>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".
>
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
===========================================================================
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".
