This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
hai i downloaded jini from sun site.I read it. i Feel that JINI MAY REPLACE SOME OF THE CONCEPTS OF EJB . I WOULD LIKE TO KNOW WHICH IS BETTER AND EASY TO IMPLEMENT EJB OR JINI. CAN ANYONE TELL ME AN REAL TIME PROJECT WHERE JINI WAS IMPLEMENTED.
EJB is somewhat easier to implement right now, as there are a lot of available off-the-shelf EJB containers and value added application servers to choose from. With Jini at the moment you have to "roll your own". Jini and EJB are really complementary rather than competetive. They cover different areas. EJB is all about encapsulating transactional access to databases and legacy systems in a structured and re-usable manner. Jini is all about amorphous networks which discover what they contain, and adjust to the appearance and disappearance of services dynamically.
Originally posted by MAGESH GOVINDARAJAN: I WOULD LIKE TO KNOW WHICH IS BETTER AND EASY TO IMPLEMENT EJB OR JINI.
Frank Carver already posted a great reply to this question, but I thought I'd add just a little more. Jini and EJB are complimentary technologies--you could, for example, use Jini "behind the scenes" to interconnect backend EJBs together. A couple of common scenarios that might indicate when or how to use Jini in an EJB scenario are: - When you want to be able to dynamically add and remove EJB components, it may make sense to use Jini so that they can discover and use each other easily, with no prior configuration. Jini will let you add redundant components, and will allow components to come and go, all without explicit configuration on the part of the programmer or administrator. - When you want a non-web front end to an EJB app, Jini can be a great way to connect your client application to your server. Not only can the client dynamically discover the server (allowing you to move it without reconfiguration), but the server also provides the client-side code necessary to use it. So there will never be any problems with the client and server getting "out of sync" version-wise. There are more complicated scenarios, of course, but these are two of the most common. Cheers, -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>.