Specification Errata

Java Card™ Platform
Version 3.0.1, Connected Edition

August 2009

Introduction
Application Programming Interface
Sample
Sending Feedback

Introduction

This page contains contains a list of important reported errata for the specifications and other documents included in the specification bundle of the Java Card™ Platform, Version 3.0.1, Connected Edition that was released May 2009.

Application Programming Interface

Location/Item Description Correction

Location/Item	Description	Correction
`javacardx.framework.JCSystem` Bug ID: 6841714	`Class` objects from application class loader should not be implicitly transferable.	Only `Class` instances corresponding to classes loaded above the application group classloaders are implicitly transferable: `Class` instances corresponding to system API and extension library classes are not bound to any context and can freely be passed across the firewall. `Class` instances corresponding to application classes are bound to their respective group context and cannot be passed across the firewall.
`com.sun.javacard.spi.cardmgmt.ApplicationGroup` Bug ID: 6850690	The semantics and handling of the `runtimeConfig` and `initParams` parameters of the `newApplication` method must be clarified and enhanced.	The semantics and handling of the `runtimeConfig` parameter has been clarified as follows: Runtime attributes already defined in the runtime descriptor can be mapped to new values. New runtime attributes not defined in the runtime descriptor can be defined. Runtime attributes already defined in the runtime descriptor can be removed by mapping the attribute names to the special `String` token "<<REMOVED>>". New runtime attributes defined in the `runtimeConfig` parameter that correspond to application properties can be retrieved by the application using the `JCSystem.getAppProperty` method. The semantics and handling of the `initParams` parameter has been clarified as follows: The method signature has been modified so that `initParams` is of type `Object` instead of `Object[]`. The new method signature is as follows: Application newApplication(String moduleName, String declaredAppURI, String requestedAppURI, Hashtable<String,String> runtimeConfig, Object initParams) When the application being instantiated is an applet application, the `initParams` value must be of type `byte[]` and must be passed as applet data in the `bArray` parameter of the `Applet.install` method. When the application being instantiated is a web application, the `initParams` value must be of type `Hashtable<String,String>`. The name/value pairs it contains must be set as `ServletContext` init parameters (retrievable by calling the `ServletContext.getInitParameter`). The new set of init parameters, if defined, overrides the complete set of init parameters defined in the web application descriptor.

javacardx.framework.JCSystem
Bug ID: 6841714

Class objects from application class loader should not be implicitly transferable.

Only Class instances corresponding to classes loaded above the application group classloaders are implicitly transferable:

Class instances corresponding to system API and extension library classes are not bound to any context and can freely be passed across the firewall.
Class instances corresponding to application classes are bound to their respective group context and cannot be passed across the firewall.

com.sun.javacard.spi.cardmgmt.ApplicationGroup
Bug ID: 6850690

The semantics and handling of the runtimeConfig and initParams parameters of the newApplication method must be clarified and enhanced.

The semantics and handling of the runtimeConfig parameter has been clarified as follows:

Runtime attributes already defined in the runtime descriptor can be mapped to new values.
New runtime attributes not defined in the runtime descriptor can be defined.
Runtime attributes already defined in the runtime descriptor can be removed by mapping the attribute names to the special String token "<<REMOVED>>".
New runtime attributes defined in the runtimeConfig parameter that correspond to application properties can be retrieved by the application using the JCSystem.getAppProperty method.

The semantics and handling of the initParams parameter has been clarified as follows:

The method signature has been modified so that initParams is of type Object instead of Object[]. The new method signature is as follows:

Application newApplication(String moduleName,
                           String declaredAppURI,
                           String requestedAppURI,
                           Hashtable<String,String> runtimeConfig,
                           Object initParams)

When the application being instantiated is an applet application, the initParams value must be of type byte[] and must be passed as applet data in the bArray parameter of the Applet.install method.
When the application being instantiated is a web application, the initParams value must be of type Hashtable<String,String>. The name/value pairs it contains must be set as ServletContext init parameters (retrievable by calling the ServletContext.getInitParameter). The new set of init parameters, if defined, overrides the complete set of init parameters defined in the web application descriptor.

Sample

Location/Item	Description	Correction

[Top]

Sending Feedback

We greatly appreciate your feedback on the specifications.