Re: Jini vs/and OSGi

Sorry for jumping in late, but I have been out of commission for long...


It is with tears[1] in my eyes I read this thread. The misconceptions on both
sides are large, and I even here disrespect among some fellows here for OSGi.
And this "impedance mismatch" between understanding each other will probably
lead to perpetual separation, exempt Newton and similar rebels.

The OSGi community's main complaint about Jini is the "undefined classloading
model". The security complaint from OSGi towards Jini is probably moot at the
advent of 2.0.

AFAIU, the Jini community's main complaint about OSGi is the attempt
at "remoteness transparency".

So both camps close the door and throw dirt at the other side's door. Bad!

Do I think it can be resolved?? Honestly; No. The mentality is lacking. Each
side refuse to educate, and be educated by, the other side.

The Jini zealots speak of all the things that can't be done if Jini is inside
OSGi. OSGi crucifies the lack of strong classloading model in Jini. The Cold
War persists.
"Man the barricades. There is an on-slaught of criticism to our perfect
technology."

I recall I tried to bring up ~9 months ago or so, the window of opportunity to
marry Jini with OSGi. Criticism here wasn't overly positive (understatement
of the day) and the window is practically closed. The OSGi Enterprise Expert
Group is not even considering Jini as a player in the field. It is WS-*, SCA,
ESBs and OSOA from one end to the other. Bandwagon mentality and mob
behavioral "me too"...

Well, I am tired defending Jini. Paremus (the Newton guys) are trying hard to
push towards a position where "Jini is possible", but from there to first
class citizen for serving the Distributed Registry, or even "allowed to be
serving the Distributed Registry" is a long way. Far too long.


So, honorable members of this community; Before you mount your white stallions
of perfection and enter a war of mud slinging, take a break and reflect over
the situation and what you could learn from "the other side". Your solution
(Jini) is not the answer to everything. It is not even the answer to most
things.
Spring Framework was in a similar position of "us vs them". But Spring
embraced OSGi, and vice versa, the synergy is good, each side is learning.
Spring is slated to become the intra-bundle component model, and OSGi is
becoming a first-class citizen in the Spring community.


hmmmm... Is there any will? Or just the will to criticize, feeling proud
and "they don't get it"??



Cheers
Niclas

[1] I happen to be in the camp of believing in both Jini and OSGi. More the
latter than the former in recent days.

--------------------------------------------------------------------------
Getting Started:     http://www.jini.org/wiki/Category:Getting_Started
Community Web Site:  http://jini.org
jini-users Archive:  http://archives.java.sun.com/archives/jini-users.html
Unsubscribing:       email "signoff JINI-USERS"  to [email protected]