Skip to main content

Phoning home

Posted by daniel on September 22, 2003 at 11:34 AM PDT

RMI is part of the J2SE stack. As more power becomes available on "limited devices" you may find J2SE running on devices that were once targets for J2ME. In the meantime, there have been several ideas on how to bring RMI to a phone near you.

JSR 66 resulted in the J2MI RMI Optional Package (RMI OP). You'll see that there are restrictions on the supported hardware that don't yet include phones. Also note that the product page also explains licensing terms.

With all of your options for distributed computing, is RMI important to you? Does RMI OP meet your needs?

A different approach is presented in the java.net project spotlight of the week: MeRMI . A member of the Java Communications community, MeRMI is designed to run on MIDP 1.0 compliant phones supporting HTTP but the alpha release has only been tested "using the J2ME Wireless Toolkit (from Sun) and on a Nokia 6610, using HTTP over GPRS on the O2 and Vodaphone networks in Ireland." The HTTP requirement because the "default implementation uses serialized data over HTTP to ensure compatability with all MIDP 1.0 implementations."

MeRMI "provides an API and tool-set for the development of applications that use RMI-like remote procedure calls from a J2ME client to a J2SE server." This means that what is produced for the server side is standard RMI. When you run mermic on your classes the result is two directories generated/j2se and generated/j2me. The quick start guide How to use MeRMI takes you through the process.

Also featured in Projects and Communities, you will find the Education and Research Community project for visualizing and animating algorithms. The JIVE project is built on top of animated data structures. The JIVE examples include graphs, binary trees, and hashtables. Support for J2SE 1.4.1is not yet ready. Join the project and offer your help.

In our featured Weblogs, James Todd's summarizes last week's JXTA community meeting in his debut post Paper AirPlanes, Tinker Toys, Grids and P2P - and I'm quite certain I wasn't lost in a neighborhood Toys "R" Us. Todd summarizes the presentations from half a dozen projects,looks ahead at future JXTA releases and summarizes the Q and A session. Joshua Marinacci considers how you would make Truly reliable software. He suggests that you "make every module be reloadable at runtime with rollback" and require redundancy in running modules and in source code in progress.

In Also in Java Today, Jakob Nielsen continues the theme of reliable software. We link to his article Time to Make Tech Work in which he presents his wish list: no bugs, Security as default, Integration, and Reliable wireless. Meanwhile, Dan Troesser looks at the nearer future in his preview of JSP 2.0 . In this Object Computing, Inc. article Troesser spends much of his time looking at the advantages of the JSTL Expression Language support in JSP 2.0 designed to make JSPs easier to create.

In today's java.net News Headlines :

Registered users can submit news items for the java.net News Page using our news submission form. All submissions go through an editorial review by news director Steve Mallet before being posted to the site. You can also subscribe to the java.net News RSS feed.

Current and upcoming Java Events:

Registered users can submit event listings for the java.net Events Page using our events submission form. All submissions go through an editorial review before being posted to the site.

This blog is delivered weekdays as the Java Today RSS feed. Once this page is no longer featured as the front page of href="http://today.java.net"> Java Today it will be archived at href="http://today.java.net/today/archive/index_09192003.html">
http://today.java.net/today/archive/index_09192003.html. You can
access other past issues in the java.net Archive.