Java News from Wednesday, August 18, 2004

Sun has posted the change log for Java Specification Request 59, J2SE Merlin Release Contents.

This document provides descriptions of specification changes being made in version 5.0 RC ("Tiger") of the JavaTM 2 Platform, Standard Edition (J2SETM).

Version 5.0 includes a set of new Java Specification Reviews (JSRs) that introduce major new functionality. This Maintenance Review does not cover new APIs defined through those JSRs; it documents only smaller changes made under the JCP Maintenance Review process.

The descriptions in this document correspond to the platform changes made since J2SE 5.0 Beta 2. The specification change descriptions are provided for purposes of Java Community ProcessSM public maintenance review.

Comments are due by September 20.

Siemens AG has posted an early draft review of Java Specification request 229, Java Payment API, "an optional package for the Java 2 Platform, Micro Edition (J2M™)" that "specifies the architecture and associated APIs that enables an open, third-party, application development environment for payment transactions." According to the draft:

The scope of this JSR is to define the following:

Both will allow 3rd party developers to build applications with control of features and services that are chargeable. The JSR API may include methods for:

The provisioning data definitions take care that service providers and payment service providers can select a suitable set of payment instruments provisioned for applications during the application deployment time. Primarily payment instruments addressed will be:

This JSR enables application developers to initiate mobile payment transactions from J2ME applications. It is an optional package for the J2ME CLDC configuration and targeted for MIDP or IMP devices. Scope of this JSR is to provide a generic payment initiation mechanism, which hides the actual payment architecture and complexity from the developers. This JSR does not define and imply any concrete payment implementation and mechanism but is generic enough to support different implementations. It is up to the implementing party to realize the API based on one or more technical solutions enabling the application initiated payment. The JSR also does not define any user behaviour or user interface but leaves them to be defined by the actual implementation of the API.

The NetBeans Project has posted the first alpha release of a profiler based on Sun Labs' JFluid. It can profile memory and CPU usage. NetBeans 3.6 is required.

Robert Oloffson has posted version 0.43 of Java Memory Profiler (JMP). JMP uses the Java Virtual Machine Profiling Interface (JVMPI) interface to track objects and method times in a JVM. It uses a GTK+ interface to display statistics. The current instance count and the total amount of memory for each class is shown as is the total time spent in each method. This release adds method callee graph and can now group object allocations to the filtered methods only. JMP is written in C for Linux.