Andy,
----- Original Message -----
From: Andy Abate <[EMAIL PROTECTED]>
To: jBoss Developer <[EMAIL PROTECTED]>
Sent: Wednesday, August 02, 2000 12:38 PM
Subject: Re: [jBoss-Dev] rmi,transactions,orbs [was: TransactionImpl]
> What is robust? Every CORBA service is designed to work in the perfect
world
> where programmers don't make mistakes, users don't go poking around the
> network and no one ever decides to try and mess anything up. They
basically
> depend on the programmers getting everything right.
> The facts are that CORBA service implementations work really well as
long
> as you don't try to use them beyond an immediate enterprise environment.
(I
> will grant that Sabre's enterprise environment is rather unique). Once you
> extend beyond a trusted arena, the "robustness" of the services fall apart
> quickly. Just try to offer a service across a NAT'ing firewall! B2B?
Without
> a common security implementation, CORBA forces the applications to use the
> security framework to negotiate their own specific protocols.
>
But we are talking about using corba as a ground on top of which build
an EJB server. Applications will use the aplication server interfaces and
not the orb ones. I said corba could be a more robust ground for the
container but not a more robust environment for the application. I would put
my trust in a JTS implemented on top of a tested ots working with a tested
orb before than in a JTA implementation that was written from scratch and
integrated in more adhoc ways with some kind of rmi-iiop orb (and here the
wheel is being reinvented too). Indeed I said CCM could be a more robust
ground for EJB. Also, I didn't preconize this as the most significant virtue
of an EJB implementation using corba.
Carlos
