Release NotesDevelopment Kit for the Java Card™ 3 Platform
|
These release notes describe the
development kit for the Java Card™ 3 Platform,
Version 3.0.2, Classic Edition, binary release.
Java Card technology combines a subset of the Java™ programming language with a runtime environment optimized for smart cards and similar small-memory embedded devices. The goal of Java Card technology is to bring many of the benefits of the Java programming language to the resource-constrained world of smart cards. The Java Card API is compatible with international standards such as ISO 7816, and industry-specific standards such as Europay, Master Card, and Visa (EMV).
Java Card platform version 3.0.2 is the latest evolution of Java Card technology. This development kit is based on the Version 3.0.1 of the Java Card Specifications, which includes their errata sheets located at http://java.sun.com/javacard/3.0.1/jc-classic-spec-errata.html. The Java Card 3 Platform consists of versions 3.0 and 3.0.1 of the specifications and versions 3.0.1 and 3.0.2 of the development kit.
For the first time, the Java Card platform is available in two editions, both of which are backward compatible with previous versions and share key security features:
Platform
Required Software
The following software must be installed for the Java Card development kit to work:
For use with the samples, the Firefox browser is considered a
trusted client by the RI. Firefox is available at http://www.mozilla.com.
Note — Do not
install any software in a directory that
contains a space in its name. For example, do not install software in
any subdirectory of c:\program files because of the space
in the program files element.
This release contains both binary and source code. Note that the Java Card specifications are not included in this release. The specifications must be downloaded separately.
This release contains features required to support classic Java Card applet applications on the card. Specifically, this release includes the following:
cref.exe)apdutool.bat)converter.bat)For a more thorough description of the installation, contents and use of the development kit, see Development User's Guide, Java Card Platform, Version 3.0.2, Classic Edition included in the download bundle for this release.
An automatic installer tool can be used to unpack the download file
containing this release. During download, you can choose to let the
installer tool unpack the download file into a directory of your choice
on your system or you can save the download file itself to your system.
Note — Do not
install development kit software in any
directory that has a space in its name. For example, on a Windows
platform, do not install software in the c:\program files
directory, or any subdirectory of c:\program files,
because the program files element contains a space.
To install the Java Card development kit and associated software, follow these steps:
Alternatively, you can use the command line to unpack the JAR file using the following command:
Where Bundle-Filename is the downloaded development kit JAR file.java -jarBundle-Filename
By default, the development kit is installed in c:\jcdk3.0.2_ClassicEdition
and its associated sub-directories. You can specify a different
directory if you wish.
The directory c:\jcdk3.0.2_ClassicEdition (or
the alternate directory you specify during installation) is referred to
as JC_CLASSIC_HOME in these
release notes. When the development
kit installation is complete, JC_CLASSIC_HOME
contains the following:
JC_CLASSIC_HOME
|
RELEASENOTES-CL-BIN.html - These
release
notes. Copyright files. |
docs |
JCDevKitUG-Classic-3_0_2.pdf
- Development Kit User's Guide for
the Java Card Platform, Version 3.0.2, Classic Edition.UserGuide.html\index.html - The user's guide in HTML. |
docs\apduio |
JavadocTM tool files for use with APDU I/O described in the user's guide. |
docs\rmiclient |
Javadoc tool files for use with optional RMI implementation described in the user's guide. |
docs\api |
Javadoc tool files for the API. |
api_export_files |
Contains java, javacard, and javacardx directories of API
export files. |
bin |
Development kit executable files. |
samples\classic_applets |
Samples of basic classic applets, such as HelloWorld. |
samples\reference_apps |
Samples of more robust classic
applets. |
lib |
Configuration and JAR files for the API, tools. Third-party libraries. |
Uninstaller\uninstaller.jar |
Uninstalls the development kit. |
legal |
License files. |
Set System Variables and Paths
System variables and paths must be set before
running the development kit. See the Development
Kit User's Guide more details on how to set them.
Note that if you choose to set the variables
and paths each time you run the development kit rather than
permanently in your system, you can place the appropriate commands in a
batch file.
JAVA_HOME. You must set the JAVA_HOME
system variable to the JDK root directory before running the
development kit.
JAVA_HOME from the command
line, enter the
command: set JAVA_HOME=c:\path before running the
development kit. For example, if the Java platform software is stored
in your c:\jdk6 directory, enter set JAVA_HOME=c:\jdk6
before running the development kit.JC_CLASSIC_HOME. You must set the JC__CLASSIC_HOME
system variable to the directory in which the development kit is
installed before running the development kit. JC_CLASSIC_HOME from the
command
line, enter the
command: set JC_CLASSIC_HOME=c:\path before
running the
development kit. For example, if the Java Card development kit is
stored
in your c:\jcdk3.0.2_ClassicEdition
directory, enter set JC_CLASSIC_HOME=c:\jcdk3.0.2_ClassicEdition
before running the development kit. ANT_HOME from the command
line, enter the
command: set PATH=c:\path before running the
development kit. For example, if Apache Ant is stored
in your c:\ant\apache-ant1.6.5
directory, enter set ANT_HOME=c:\ant\apache-ant1.6.5
before running the development kit. MinGW before running the
development kit. Note that the path has to
point to the \bin subdirectory of the MinGW installation
directory where the gcc.exe file is located.
set
PATH=c:\MinGW_path;%PATH%. For example, if MinGW is
installed in c:\MinGW, enter the command set
PATH=c:\MinGW\bin;%PATH% before running the development kit.Configure the Java Card Runtime
Environment for the Samples
Note that the Java Card RE (cref)
implementation is not optimized for memory or performance and,
therefore, requires more memory than an actual optimized implementation
on a card. To run the
Java Card RE, you can use the default executable, cref.bat, using the command
line as follows:
JC_CLASSIC_HOME\bin\cref.bat
To remove this development kit, an automatic uninstaller tool is
provided in the directory Uninstaller. You can also completely remove
the development kit by deleting the JC_CLASSIC_HOME
directory along with all of its contents.
| BUG ID | DESCRIPTION |
|---|---|
| 6903384 |
Converter fails to generate cap
file if an applet imports some.other.package.Shareable interface. |
| 6905812 |
Verifier fails when .cap contains
incorrect data in class_debug_info.interface_names_indexes section. |
The public Java Card technology web site is http://java.sun.com/javacard. The developer collaboration web site also contains information about Java Card technology at http://kenai.com/projects/javacard/pages/HOME.
If you are a Licensee, visit the product web site at https://java-partner.sun.com/portal/service/ent/platform/javacardgroup This site has the most up-to-date information on the following:
We greatly appreciate your feedback on this reference Implementation. Please send all feedback to jc3-ri-feedback@sun.com.
Copyright
© 2009 Sun Microsystems, Inc. All rights reserved.
Sun Microsystems, Inc. has intellectual property
rights relating to
technology embodied in the product that is described in this
document. In particular, and without limitation, these intellectual
property rights may include one or more of the U.S. patents listed at
http://www.sun.com/patents
and one or more additional patents or pending patent applications in
the U.S. and in other countries.
U.S. Government Rights - Commercial Software. Government users are
subject to the Sun Microsystems, Inc. standard license agreement and
applicable provisions of the FAR and its supplements.