This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
It looks like Jini is designed to complement J2EE, as well as other "legacy" infrastructures. Jini is a from-the-ground-up implementation of a robust and manageable distributed processing system, and makes as much sense when used within an enterprise application as within a network of devices. because J2EE and Jini both use Java, they can work seamlessly together. In a very simple example, if you want a web-browser view of some information or services from a Jini federation, you would use a J2EE servlet/JSP container to handle the HTTP/HTML and Jini or JavaSpaces to access the data or services. This is how I'm using Jini at the moment, as it requires no Java on the client machines.
As far as Jini being used in devices, I think it will probably be widely accepted in just about every communications device like laptops, and cell phones. ------------------ I wish there was a button on my monitor to turn up the intellegince. Theres a button called 'brightness' but it doesn't work
"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."
Originally posted by Latha Kalaga: Hi Keith, I am curious about the future of Jini. With sun making a big push for J2EE, does anyone have any opinion as to how J2EE and Jini can co-exist and compliment each other? Thanks
Jini and J2EE are complimentary technologies--J2EE is (at least partially) about creating a component framework around various bits of enterprise technologies, like databases, app servers, etc. Jini is about how components get interconnected. In particular, Jini affords a very dynamic sort of interconnection, where components can come and go in a very light weight way, automatically find out about each other, and so on. IMHO, Jini will initially be used as a way to interconnect software services, including backend EJB components...not initially as a hardware interconnect, as Sun promotes it. -keith
<a href="http://www.kedwards.com/jini" target="_blank" rel="nofollow">Keith Edwards</a><br />xerox palo alto research center<br />author of: <a href="http://www.amazon.com/exec/obidos/ASIN/0130894087/keithedwards" target="_blank" rel="nofollow">Core Jini</a><br />Which is also available as <a href="http://www.amazon.com/exec/obidos/ASIN/0130863866/keithedwards" target="_blank" rel="nofollow">A Video Course</a><br />Read an Example Chapter - <a href="http://www.javaranch.com/bunkhouse/samps/Core_Jini_chap3.pdf" target="_blank" rel="nofollow">Chapter 3</a> or <a href="http://www.javaranch.com/bunkhouse/samps/Core_Jini_chap10.pdf" target="_blank" rel="nofollow">Chapter 10</a>.
Hi Keith, One thing that hits me about JINI it ability to allow even hardware oriented services to delivered thru the network. Can You elaborate for instance how the hell will Car sense that The gas in the tank has gone down & send a mailer to me for refilling of the gas or send a request notification to gas station with a authenticated request for gas filling. Its okay when we say software service being plugged in plugged out of the network but whats happening how does the car understand that the petrol is down how does it know it has to send notification to the following gas station server etc... Is it lot of rut, i hope u will help me make more sense. Regards Tushar ------------------
Joined: Jan 02, 2001
Originally posted by Tushar Kansara: Hi Keith, One thing that hits me about JINI it ability to allow even hardware oriented services to delivered thru the network. Can You elaborate for instance how the hell will Car sense that The gas in the tank has gone down & send a mailer to me for refilling of the gas or send a request notification to gas station with a authenticated request for gas filling.
Well, the scenario you just mentioned really has nothing to do with Jini. Jini is about dynamically interconnecting bits of software on a network in very fluid and robust ways. Now, of course, if you have some sensors on your can that can detect the gas level and report it to a processor that's on the network somewhere, you could certainly turn this into a Jini service and build the sort of application you're describing. But Jini isn't some magic that will, out of the box, cause your car to send you email. :-) -keith