Extended CAP File Manifest File Syntax
An extended CAP file utilizes the JAR file format, and has the same properties as a compact CAP file. However, there are some differences in the way the information that is specific to the extended CAP file is represented in the META-INF/MANIFEST.MF file.
The following table lists the names in the manifest file that are specific to the Java Card packages and Java Card Applets. These fields are changed to consider the extended CAP file context:
The information in the manifest file is presented in name:value pairs. These name:value pairs are described in Sample Extended CAP Manifest File .
Table 5-2 Extended CAP File Manifest File Name Syntax
| Name | Changed To: | Change Description |
|---|---|---|
|
|
|
An extended CAP file can have multiple packages. Therefore, an index is added for each package name. |
|
|
|
An extended CAP file can have multiple packages. Therefore, an index is added for each package version. If the package is not exported (private or applet package with no shareable interfaces), the value of this field is set to |
|
|
|
An extended CAP file can have multiple packages. Therefore, the package that contains the applet is added for each applet AID. |
|
|
|
An extended CAP file can have multiple packages. Therefore, the package that contains the applet is added for each applet name. |
Some new name:value pairs are added in the extended CAP manifest file. These name value pairs have extended CAP file-specific information. The following table lists and describes the new name value pairs.
Table 5-3 Name:Value Pairs in the extended CAP MANIFEST.MF File
| Name | Value |
|---|---|
|
|
The extended CAP file name as defined in the |
|
|
The extended CAP file AID as present in the header component of the CAP file. |
|
|
The extended CAP file version as present in the header component of the CAP file. |