Extract sibling .cod files.

To ensure a BlackBerry® device user does not override the original .cod file, on the content server, extract the sibling .cod files into a different directory than the directory where the original file exists.
  1. Unzip the original .cod file and extract the sibling .cod files.
  2. Place each sibling .cod file on a content server.
  3. In the .jad file, list the sibling .cod files separately. Use the following naming convention for sibling .cod files: name of original .cod file - sequential number.
  4. Create a RIM-COD-URL-<#> parameter for each sibling .cod file, and place the name of the sibling file to the right of this parameter. # is a number that starts at 1 and increases by 1 for each sibling file. Give each sibling .cod files the same name as the original .cod file, followed by -<#>.
  5. Create a RIM-COD-Size-<#> parameter for each sibling .cod file, and place the size of the sibling file to the right of this parameter. # is the same number that is appended to the name of the sibling file. Place the RIM-COD-Size-<#> parameter immediately below the RIM-COD=URL-<#> parameter.

Example: Listing sibling .cod files in a .jad file

The following example contains two sibling files named myApp-1.cod and myApp-2.cod, after the original .cod file myAPP. The developer appends the ‘.cod’ file extension to each sibling file name. The developer creates a RIM-COD-Size-<#> parameter for each sibling file.

Manifest-Version: 1.0
MIDlet-Version: 1.0.0
MIDlet-1: ,,
RIM-COD-Module-Dependencies: net_rim_cldc
MicroEdition-Configuration: CLDC-1.0
RIM-COD-Module-Name: MyApp
MIDlet-Name: My Application
RIM-COD-URL: myApp.cod
RIM-COD-Size: 55000
RIM-COD-URL-1: myApp-1.cod
RIM-COD-Size-1: 50000
RIM-COD-URL-2: myApp-2.cod
RIM-COD-Size-2: 25000
MicroEdition-Profile: MIDP-1.0

Index


Was this information helpful? Send us your comments.