Skip to main content

J2SE in your pocket

Posted by daniel on April 18, 2005 at 2:45 AM PDT

J2SE in the embedded space

Ted Kosan applauds One Small Change for a Page, One Giant Leap for J2SE in today's href=""> Weblogs . " While much of the Java community has been busy battling in the J2EE/.NET wars, the Law of Accelerating Returns has been relentlessly pushing microelectronics into the microcosm. All of a sudden, J2SE 5.0-capable embedded systems about the size of a dollar bill are about to hit the market and I think this has the potential to cause a significant paradigm-shift in the overall Java community."

Meanwhile, Tim Boudreau is fighting a different sort of war and publishes his opinion piece Am I the only one who finds Eclipse's governance just bizarre? As you might expect, our readers have taken the time to answer his question.

Roger Brinkley has posted an announcement about tomorrow's JDK Contribution Chat. Peabody engineers Peter Kessler and Kelly O'Hair will be taking your questions April 19 at 10 am PDT.

Some of us remember the past by pulling out old photographs. In Ludovic Chamenois' post Java 10 years... he looks back at a bug filed in 1995 noting " Already our Java engineers were obsessed by cross-platform portability, even working during regular lunch time (1:34 PM), on multi systems, clock synchronized to produce similar output, precise at the second."

In Also in
Java Today
, Don Schwarz has a question for dealing with your application's third-party jars: what if they depend on other jars? More critically, what if some of them depend on different versions of the same jar? This is a potential nightmare, whose hazards might only appear at runtime, and for which several bad solutions are seen in the wild. But there's a better way. In Managing Component Dependencies Using ClassLoaders, he shows how to use a jar-file attribute and a custom class loader to allow each library to explicitly state its dependencies and have them honored.

Lonneke Dikmans is the author of the final part in the twelve part OTN series "Mastering J2EE Application Development" with Deployment: Where the Rubber Meets the Road "What makes deployment so complex? Let's look at a typical enterprise application. Invariably, enterprise applications have three different layers: presentation, business services, and a persistence layer. Each layer can be packaged as a separate J2EE module, destined for one or more instances of a target container—each of which can be located on a single application server or across multiple servers (for example, for load balancing purposes)."

In Projects and
, the Mac Java Community page notes a thread on the Apple java-dev list discussing how Java developers can get toolbar and document icons that resemble their native OS X counterparts. Those interested in native integration issues may also want to check out the JDIC project.

Ed Ort writes about "the potential of [...] a web services-based SOA -- in dramatically speeding up the application development process." In his article Service-Oriented Architectures and Web Services, he surveys the standards and emerging protocols for SOA's, and support for them in Java.

Scott Ellsworth advocates that we Require server VM implementation in today's Forums. "Previous statements say that the server and client VMs are going to be different beasts in Mustang, as they are in Tiger. Some vendors (Apple, for one) have been known to drag their feet on implementing the server VM. I thus have a modest proposal. Require a server VM implementation as part of the JCK for Mustang. This will require vendors to provide the option, and will thus insure that the performance numbers for Mustang will include the -server flag where it is appropriate."

Tackline adds to the thread on Collections improvements (read-only interfaces). "1.5 did at one point have read only supertypes of Iterator and Iterable, SimpleIterator and SimpleIterable. Covariant return types are implemented by javac adding bridging methods in the class that (first) implements the interfaces. In the 1.5 proposed collections case, classes implementing Iterable, including all those implementing Collection, will forward from iterator()Ljava/util/SimpleIterator; to iterator()Ljava/util/Iterator;."

In today's
News Headlines

Registered users can submit news items for the href=""> News Page using our
news submission
. All submissions go through an editorial review before being
posted to the site. You can also subscribe to the href=""> News RSS

Current and upcoming Java

Registered users can submit event listings for the href=""> Events Page using our href=""> events submission form.
All submissions go through an editorial review before being posted to the

Archives and Subscriptions: This blog is delivered weekdays as
the Java
Today RSS feed
. Also, once this page is no longer featured as the
front page of it will be
archived along with other past issues in the href=""> Archive.

J2SE in the embedded space