(CC'ed to jboss-dev) On Fri, 11 Aug 2000 09:44:35 +0200, Jon Finanger <[EMAIL PROTECTED]> wrote: >Does anyone have a comment on how to combine these technologies? Has anyone >done that already - whats your experiences? Most interesting question, but it needs to change slightly: How can Jini be used with J2EE? Now there's the $1.000.000 dollar Q. There has been some projects to this end (AFAIK), some of which were presented at this years J1, for example: http://jsp.java.sun.com/javaone/javaone2000/event.jsp?eventId=1067&trackId=5&eventType=TS&ts=965980311581 However, these seems mostly to be "on top" usage of Jini and J2EE. What I see as more interesting is when Jini is used *inside* of the actual J2EE implementation. As a coincidence(?), since I am one of the core developers at jBoss.org (OpenSource J2EE-ish app server), this possibility has intrigued me for a while. I see the use of Jini in a J2EE implementation in these particular areas: * To implement a JNDI naming service. Currently most implementations require the client to know the provider host, where the actual service is. If this is done internally by using Jini, it would be sufficient to say "Get me the JNDI service at this location", or "Get me the JNDI service for this cluster". Etc. The possible reductions in administration of client configurations are huge. * To implement EJB clusters. Jini could be used to both allow clusters to form by letting cluster nodes discover each other dynamically, but the fault-tolerance built into Jini is also ideal for implementing fail-over functionality when invoking the EJB services in the cluster. Load-balancing is also made easier because of the nodes ability to describe their abilities through the Jini service attributes. * To implement JMS clusters. Basically the same thing, but for JMS instead. Router topology can be managed automatically by letting JMS nodes discover each other dynamiclly. * To implement JMX management tools. J2EE server should IMHO all be managed through JMX, and by creating JMX management adaptors with Jini, the management tools would become incredibly cool, allowing an administrator to easily get a view of the currently running nodes, and the ability to manage them remotely. These are just some ideas I've had on how to marry these two technologies. We will see how it works out, but I expect it to be nothing less than revolutionary in terms of the levels of easy of use and flexibility introduced. Comments? /Rickard -- Rickard �berg Email: [EMAIL PROTECTED] http://www.telkel.com http://www.jboss.org http://www.dreambean.com
