Cep Terminals GSM/GPRS TERMINAL CT63 JAVA 6203 사용자 설명서
제품 코드
6203
Java User’s Guide
8.12 Incremental OTAP
54
wm_java_usersguide_v19
Page 54 of 109
2012-01-27
Confidential / Released
Jad file example:
Corresponding manifest file example:
If the liblet is signed the attributes
•
•
MicroEdition-Configuration
•
MicroEdition-Profile
also need to be corresponding in both files if they exist.
The jad file of the midlet needs to be extended to specify the liblets needed, e.g.
The numbering starts with 1 and has to be continuous. The "Dependency" attribute consists of
name, vendor, version and "liblet"-keyword, all separated by semicolons.
name, vendor, version and "liblet"-keyword, all separated by semicolons.
The name is used to identify a liblet. It has to correspond with the name attribute of the liblet.
Vendor and "liblet" entries are currently unused.
Vendor and "liblet" entries are currently unused.
The OTAP install/update process still always starts with the download of the midlets jad file.
After that only the parts which are necessary (i.e. version number in descriptor differ from in-
stalled version number) are downloaded and installed into the Application Directory.
After that only the parts which are necessary (i.e. version number in descriptor differ from in-
stalled version number) are downloaded and installed into the Application Directory.
PRE-deletion (i.e. remove an old jar file before download of the new one in order to make room
in the ffs) of installed files is not supported for incremental OTAP.
in the ffs) of installed files is not supported for incremental OTAP.
There is only one result posted at the end of the whole OTAP process. The URL for that can
(as usual) be specified by the otap at command or be included in a jad file. When multiple jad
files involved in the process contain a NotifyURL the one from the file which was processed last
is used. So you could e.g. put a different NotifyURL into each jad file, that will give you an extra
hint at what point the OTAP process went wrong.
(as usual) be specified by the otap at command or be included in a jad file. When multiple jad
files involved in the process contain a NotifyURL the one from the file which was processed last
is used. So you could e.g. put a different NotifyURL into each jad file, that will give you an extra
hint at what point the OTAP process went wrong.
The name of the attribute is the same in all jad files: MIDlet-Install-Notify or MIDlet-Delete-No-
tify
tify
LIBlet-Name: network
LIBlet-Version: 2.0.0
LIBlet-Vendor: Customer Inc.
LIBlet-Jar-Size: 1259
LIBlet-Jar-URL: http://customer.server.com/otap/network.jar
LIBlet-Version: 2.0.0
LIBlet-Vendor: Customer Inc.
LIBlet-Jar-Size: 1259
LIBlet-Jar-URL: http://customer.server.com/otap/network.jar
LIBlet-Name: network
LIBlet-Version: 2.0.0
LIBlet-Vendor: Customer Inc.
LIBlet-Version: 2.0.0
LIBlet-Vendor: Customer Inc.
Dependency-1: at; Customer Inc. ; 1.1.2; liblet
LIBlet-Dependency-JAD-URL-1: http://customer.server.com/otap/at.jad
Dependency-2: network; Customer Inc. ; 2.0.0; liblet
LIBlet-Dependency-JAD-URL-2: http://customer.server.com/otap/network.jad
LIBlet-Dependency-JAD-URL-1: http://customer.server.com/otap/at.jad
Dependency-2: network; Customer Inc. ; 2.0.0; liblet
LIBlet-Dependency-JAD-URL-2: http://customer.server.com/otap/network.jad