Migrating Device Applications

Device applications created in Unwired Platform 1.0 or 1.2 are automatically updated for version 1.5.5.

Migration of device application files from Sybase Unwired Platform 1.0 and 1.2 to 1.5.5 is automatic when you:
  1. Open the version 1.0 or 1.2 device application file.
    Note: Device applications created in Unwired Platform versions earlier than 1.2 are migrated to version 1.2 and then migrated to version 1.5.5.
  2. Save the device application file.
  3. Re-deploy the device application file.
When opening device application files from earlier Unwired Platform versions, the device application is updated or changed in the following ways:
Feature Change
User templates Version control will be added to user template screens. When a create or delete is performed on a template screen, if the template screen’s version is not current, the template screen migration will be performed on each of the user template screens.

Template screens that are not migrated are written to a template_screen_name.xml.bad file.

Styles Device Application Designer after 1.5.2 uses style sets instead of styles, so the style definition of versions earlier than 1.5.2 are no longer valid. When an earlier version of the device application file is opened, the XML structure of the style is silently modified.
Tab folder and tab panel Tab folders can no longer have any sibling controls on the display. When a device application file is opened, if there are controls outside of tab folders, they are removed.

Actions that reference removed controls are reported by problem check.

Tab panel

When device application files that have controls within a tab panel are opened, the controls are silently moved to the panel display.

Headers and footers Headers and footers are no longer used and are silently removed.
Stock screen properties Unused and unsupported stock screen properties are removed when the device application file is opened. Platform-specific properties are moved to the RIM section.
Stock screens The About, Push Settings, Screen Saver, and Profile stock screens are now settings screens. When a device application file that contains these screens is opened, those stock screens are removed, as well as connections to and from those screens.
Radio button Style definitions are now defined once for all Radio Buttons within a Radio Group. The style that was assigned to the Radio Button with the lowest ID is now used for the Radio Group.

A text_equals_value attribute has been added to the radio button element definition. During migration, it is checked for each radio button and if the name and the value are identical, the text_equals_value attribute is set to true and the value attribute is removed.

If the value is uniquely defined or defined as NULL, the text_equals_value attribute is set to false.

Menu items When a Device Application Designer containing device context menus and Unwired Platform context menus is opened, the create, update, delete, details, and relationship context menu items are silently removed.
Hyperlink During migration the hyperlink attribute activation will be removed if it was set, because the logical type is unknown. Verify the device application file and use the content assist feature to define the logical types.
Related concepts
Preferences
Related tasks
Downloading the BlackBerry JDE and MDS Simulator
Installing the BlackBerry Java Plug-in for Eclipse
Configuring Unwired Server to Use HTTPS for Replication Sync
Related reference
Windows Mobile Client Application .DLL Dependencies