1. Development Kit User Guide
  2. Setup, Samples and Tools
  3. Converting and Exporting Java Class Files
  4. Overview of Converting and Exporting Java Class Files
  5. Using the Converter in the Compact or Extended Format

Using the Converter in the Compact or Extended Format

The selection of the format (either compact or extended) depends on the following factors:

  • Application Design
    • The number of Java packages included in the application - If the application (or library) only includes a single package, it can be converted into a compact file format.
    • The total code size - If the application code creates a method component with a size larger than 64 K, then the extended format is required.
  • Deployment Constraints
    • Some libraries must remain private - If an application relies on libraries that must not be shared, the extended format can be used to support application made of multiple packages instead of refactoring the code and copying the library classes into the application package.
    • A shared library includes both a public API made of one or more exported packages and private implementation packages - This could be achieved using an extended format CAP file that contains both parts, keeping the implementation packages private, and deploying all packages in one CAP file.

The format (compact or extended) can be set using the Converter command line parameters. See Running the Converter, for more details about the command line parameters. See Programming for Multipackage Large CAP Files, for more details about the Extended CAP file.