Talip Ozturk writes about
J2EE
and Jini and what is relationship between them:
(...)They are not truely competing technologies rather complementary
technologies. if you are writing a J2EE server, you can use Jini's dynamic, self
healing features. if a Jini service needs to persist data in a way that entity
beans does, then the Jini service can make use of a J2EE server to do that. if
you are writing JMS implementation, you might want to leverage Jini JavaSpaces
technology. JNDI might internally be interfacing with Jini Lookup Service to
gain some dynamic behaviour.(...)
I think that distributed computing is changing with advent of Web Services
and in particular Grids. The feature may be something like distributed
container that is dynamically created from available services (similar to
Jini but on Internet scale) that guaranteed to have all required resources such
as performance, bandwidth, transactions etc. as described in SLA, QoS, ... (in
this respect it is meeting and superseding requirements of J2EE).
Anyway only future can really tell and some technologies seem to stay longer
(or shorter) than predicted.