Each CAP file component is represented as a single file. The component file names are enumerated in TABLE 6-2. These names are not case sensitive.

Component Type

File Name

COMPONENT_Header

Header.cap

COMPONENT_Directory

Directory.cap

COMPONENT_Applet

Applet.cap

COMPONENT_Import

Import.cap

COMPONENT_ConstantPool

ConstantPool.cap

COMPONENT_Class

Class.cap

COMPONENT_Method

Method.cap

COMPONENT_StaticField

StaticField.cap

COMPONENT_ReferenceLocation

RefLocation.cap

COMPONENT_Export

Export.cap

COMPONENT_Descriptor

Descriptor.cap

COMPONENT_Debug

Debug.cap

All CAP file components are stored in a JAR file. As described in Section 4.1.3, JAR File Container, the path to the CAP file component files in a JAR file consists of a directory called javacard that is in a subdirectory representing the package's directory. For example, the CAP file component files of the package javacard.framework are located in the subdirectory javacard/framework/javacard. Other files, including other CAP files, may also reside in a JAR file that contains CAP file component files.

The JAR file format provides a vehicle suitable for the distribution of CAP file components. It is not intended or required that the JAR file format be used as the load file format for loading CAP file components onto a Java Card technology-enabled device. See Section 6.2, Installation for more information.

The name of a JAR file containing CAP file components is not defined as part of this specification. The naming convention used by the Sun Microsystems, Inc. Java Card Converter Tool is to append .cap to the simple (meaning not fully qualified) package name. For example, the CAP file produced for the package com.sun.javacard.JavaLoyalty would be named JavaLoyalty.cap.