The Jini Community has approved the ServiceUI API, the first standard that has passed through the Jini Community Decision Process (JDP). The ServiceUI API standardizes an approach for attaching user interfaces to individual Jini technology-based services. In related news, a Sun official said that Jini technology may have found its niche as a component of on-demand computing.
- Posted by: Floyd Marinescu
- Posted on: May 08 2003 11:45 EDT
http://serviceui.jini.org and read the artima.com press release (Artima originally contributed the ServiceUI API).
Read Sun's Jini May Find Home In On-Demand Computing.
I am happy to see that the underground movement around Jini is growing.
Jini goes one step forward compared to any other enterprise solution. Even if it may not succeed right now, the Jini way of doing things is what we all will use in a few years.
Application servers should be done over in a service-oriented manner. The J2EE/.Net approach is too limited and constraining, and in no way easier!
Jini is great because it runs around your code, it doesn't rewrite it for its internal usage. Recently I have been working at a project where the code was all made of Jini services. When I was asked to make it one block (you know, remove all remote calls for local ones) I did it in one day.
Try refactoring all your ejbs in one standalone jar.
The other beauty of Jini is that it is scalable by design.
Have a good one.
Jini is an excellent technology and will have its time very soon. There are some excellent open source projects that allow developers to create some really cool enterprise apps.
A Distributed Jini Bean framework, an alternative to the J2EE Enterprise Bean.
Has an Entity Service Bean framework for interacting with a transactional compliant database.
And a Distributed State Service Bean framework for writing general Jini Services. A Printer Service for Example.
A JavaSpaces service supported by a relational database back-end
Excellent replacement for JMS.
A Dynamic Service Provisioning Platform
Im using a combination of all these technologies and have found them to be a perfect replacement for the existing J2EE technolgies.
I hope there will be more standard from JDP.
I am developing some Jini services for mobile devices (PDA, cellphone) using Surrogate Architecture.
Jini ease my life and made my programming becoming fun and fast ;)
I have heard a great deal, but seen little on how JINI can sit as a services layer on top of existing J2EE applications. Re-writting every legacy J2EE app as JINI is not a reasonable task for most situations.
The idea of JINI technology sitting on top of existing apps as a service oriented framework is very interesting. I think that Marco has claimed success with this strategy. Are there any links / examples discussing some of these issues (NOT the Tomcat cluster doc from gigaspaces)