BlackBerry

• The sup_client2.jar client is now shipped as a library, with no separate sup_client2.cod and sup_client2.alx files. This requires a change to how you develop BlackBerry projects:

  • Eclipse projects – export sup_client2.jar into the build path configuration.
  • BlackBerry JDE projects – create a library project including sup_client2.jar.

• Several client files have been deleted in version 2.2 SP02: CommonClientLib, MessagingClientLib, MocaClientLib files, and MCL.jar substitutes. However, MCL.jar packages and classes are shipped into sup_client2.jar, so change your application to reference sup_client2.jar and UltraliteJ12.jar

For information and examples for migrating existing BlackBerry applications to 2.2 SP02 implementing these changes, see Migrating BlackBerry Applications (Eclipse Project) and Migrating BlackBerry Applications (JDE Project).

To learn more about the BlackBerry Password Based Code Signing Authority on which the API is based, and about the parameter signerId: http://supportforums.blackberry.com/t5/Java-Development/Protect-persistent-objects-from-access-by-unauthorized/ta-p/524282.

To download the BlackBerry signing tool used with this new API: https://swdownloads.blackberry.com/Downloads/entry.do?code=D82118376DF344B0010F53909B961DB3.

For information and examples for migrating existing BlackBerry applications to 2.2 SP02 implementing this change, see Migrating BlackBerry Applications (Eclipse Project) and Migrating BlackBerry Applications (JDE Project).