Find JSRs
Submit this Search


Ad Banner
 
 
 
 

JSR 256 MR 1.2 Change Log

JSR 256 Maintenance Release 1.2 Change Log (15 Sep, 2008)

 

The following table provides the list of issues addressed by the JSR 256 Expert Group during the 1.2 maintenance phase, including the proposed changes to the specification that will benefit the users (application developers, content providers, and implementers) of JSR 256 specification.

 

#

Issue

Description

Change

Status

1

Appendix B. New permissions

Permissions inherited from java.security.Permission to be defined

To provide javax.microedition.sensor.SensorPermission and javax.microedition.sensor.SensorProtocolPermission classes.

In addition to the new chapter in Appendix B. also the actual classes must be provided. Adding new classes has also an influence on TCK signature tests.

PROPOSED

2

Appendix E. Sensor definitions

 

There have been customer requests for sensor definition recommendations. The recommendations will help in unifying the sensor implementations accross different manufacturer platforms. In the maintenance release 1.2 "double_tap" sensor definition is added. "gesture" and "multi_touch" sensors are proposed and have to be evaluated during the process; adding these sensors has not been decided yet.

The modified Appendix E will describe needed information for selected sensors, such as data type, unit, and measurement rates.


Sensor definitions mean information that is needed in populating a SensorInfo and a ChannelInfo objects. All the information cannot be defined, because it is vendor specific.

PROPOSED

3

Missing quantities in SensorInfo

There exist sensors whose quantity is missing from the list stated in SensorInfo.

"double_tap" and "charger_state" are added to the list.

PROPOSED

4

SensorInfo: PROP_PERMISSION

A new property to show needed permissions

To provide a new property PROP_PERMISSION the values of which may be "javax.microedition.sensor.PrivateSensor", "javax.microedition.sensor.ProtectedSensor", or comma-separated list of both. Missing property implies a public sensor.

PROPOSED