Motorola E680 Technical Manual - Page 20

Application Management - case

Get Motorola E680 - Smartphone - GSM PDF manuals and user guides View all Motorola E680 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 20 highlights

5 Application Management The following sections describe the application management scheme for the Motorola E680 handset. This chapter will discuss the following: • Downloading a JAR without a JAD • MIDlet upgrade • Installation and Deletion Status Reports Downloading a JAR file without a JAD In Motorola's MIDP 2.0 implementation, a JAR file can be downloaded without a JAD. In this case, the user clicks on a link for a JAR file, the file is downloaded, and a confirmation will be obtained before the installation begins. The information presented is obtained from the JAR manifest instead of the JAD. MIDlet Upgrade Rules from the JSR 118 will be followed to help determine if the data from an old MIDlet should be preserved during a MIDlet upgrade. When these rules cannot determine if the RMS should be preserved, the user will be given an option to preserve the data. The following conditions are used to determine if data can be saved: • The data is saved if the new MIDlet-version is the same or newer, and if the new MIDlet-data-space requirements is the same or more than the current MIDlet. • The data is not saved if the new MIDlet-data-space requirement is smaller than the current MIDlet requirement. • The data is not saved if the new MIDlet-version is older than the current version. If the data cannot be saved, the user will be warned about losing data. If the user proceeds, the application will be downloaded. If the user decides to save the data from the current MIDlet, the data will be preserved during the upgrade and the data will be made available for the new application. In any case, an unsigned MIDlet will not be allowed to update a signed MIDlet. 20

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
20
5
Application Management
The following sections describe the application management scheme for the Motorola
E680 handset. This chapter will discuss the following:
•
Downloading a JAR without a JAD
•
MIDlet upgrade
•
Installation and Deletion Status Reports
Downloading a JAR file without a JAD
In Motorola’s MIDP 2.0 implementation, a JAR file can be downloaded without a JAD. In
this case, the user clicks on a link for a JAR file, the file is downloaded, and a confirmation
will be obtained before the installation begins. The information presented is obtained from
the JAR manifest instead of the JAD.
MIDlet Upgrade
Rules from the JSR 118 will be followed to help determine if the data from an old MIDlet
should be preserved during a MIDlet upgrade. When these rules cannot determine if the
RMS should be preserved, the user will be given an option to preserve the data.
The following conditions are used to determine if data can be saved:
•
The data is saved if the new MIDlet-version is the same or newer, and if the new
MIDlet-data-space requirements is the same or more than the current MIDlet.
•
The data is not saved if the new MIDlet-data-space requirement is smaller than
the current MIDlet requirement.
•
The data is not saved if the new MIDlet-version is older than the current version.
If the data cannot be saved, the user will be warned about losing data. If the user
proceeds, the application will be downloaded. If the user decides to save the data from
the current MIDlet, the data will be preserved during the upgrade and the data will be
made available for the new application. In any case, an unsigned MIDlet will not be
allowed to update a signed MIDlet.