Jini vs. CORBA

From Jini.org

Actually Jini only uses CORBA or any other distributed programing protocol so this is not a fair comparison.

It is important to understand that CORBA is a communications protocol, in that it defines how: connections are established, requests are sent, how parameters are encoded, responses are read, and so on. Jini, on the other hand, is an architecture for distributed components where communication protocols are a required aspect to achieve that. See (What is Jini?).

Corba and Jini offer some similar functionality, including distributed events, transaction support, lookup, among others. But these are fundamentally different because the programming model is fundamentally different. In many aspects Jini comes to overcome many of the problems found in CORBA (and RMI) on a practical level, and offers a structure that is incomparably more flexible.

But CORBA has its advantages, including through the IDL and generally available protocol definitions CORBA can accommodate any programming language with no extra work (on the part of the product developer). But please note that most of the infrastructure solutions (namely the ORB) to run a CORBA network is payed.

Finally Jini is protocol agnostic but can be deployed using CORBA. Just remember, Jini USES CORBA and that there is no comparison.