Discovery Processors

During the Discovery Process, the user is given the opportunity to select specific File Naming policies, MIDlet, Android and Blackberry pre-processors to run against the assets the user intends to discover into Metaflow.

The Images below demonstrate the different processors the user can select.

Discovery File Naming Policies

Select the discovery file naming policies to use.


Caption 1: File name policies

  1. Symbian Binary Locale Extraction: Extracts the supported locale from the discovered binary.


  2. Android Locale Extraction: Extracts the supported locale from the discovered binary.


  3. Locale: Scans for language names separated by underscores e.g."_en".


  4. Device: Scans for device names separated by underscores e.g."_6630".

Please note that discovery file naming policies are used to attempt to calculate information from the file name of any assets found in the project folder. This will attempt to fill in fields in the remainder of the wizard. However, this information can be edited during the wizard and also afterwards using the bundle editor.

MIDlet Processors


Caption 2: MIDlet processors

  1. Properties Match: Ensures that all matching attributes within the Jad and Manifest contain the same values.


  2. Icon: Validates MIDlet-1 and MIDlet-Icon equality and icon type


  3. MIDlet-: Tests all occurences of the MIDlet- attribute against JSR37 requirements (see JCP.ORG)


  4. MIDlet Class: Tests for presence of MIDlet class in the jar file


  5. Icon Presence: Tests for presence of icons in the jar file


  6. Jar Content Scanner: Tests for present of file with specified regular expression


  7. Attribute Name: Tests for illegal characters in the jad and manifest attribute names.
The main functions performed are:

  1. To ensure correct new line sequences in jad and manifest files


  2. To ensure all JSR37 MIDP properties are present (jad file always wins if differing values found in JAD/JAR pairs)

  3. To ensure all discovery Midlet attribute logic is applied
The MIDlet Jar Content Scanner

This feature allows further discovery processing of the MIDLet JAR and is set up via Preferences > Discovery Preferences > MIDlet Jar content scanner. The user can add various PERL regular expressions to search for specific file names within the Jar (Shown in Caption 3).


Caption 3: Shows strings that will be ignored .

Android Processors


Caption 4: Android Processors

  1. Sha1 Processor: This processor uses the Android toolkit to validate the Sha1 values


  2. Android Manifest XML: Test for the presence of the AndroidManifest.xml in the APK file

Blackberry Processors


Caption 5: Blackberry Processors

  1. Properties Match: Validates all matching attributes within the JAD and COD Manifest contain the same values


  2. Icon: Validates MIDlet-1 and MIDlet-Icon equality and icon type


  3. MIDlet-: Test all occurrences of the MIDlet-n attribute against JSR 37 requirements


  4. Main Class: Test for the presence of MIDlet class in the COD file


  5. Icon Presence: Tests for the presence of icons in the COD file


  6. Attribute Name: Tests for illegal characters in the JAD attribute names


  7. RIM-COD-SHA1(s) present in JAD: Ensures all required RIM-COD-SHA1 attributes are present in the Blackberry JAD


  8. RIM-COD-SIZE(s) present in JAD: Ensures all required RIM-COD-SIZE attributes are present in the Blackberry JAD


  9. RIM-COD-URL(s) present in JAD: Ensures all required RIM-COD-URL attributes are present in the Blackberry JAD


  10. COD Siblings present in CSA: Ensures all siblings referenced by RIM-COD-URL attributes in the JAD are present in the COD sibling archive