|
|
Classification: |
Java |
Category: |
J2ME MIDP |
Created: |
02/21/2005 |
Modified: |
03/08/2005 |
Number: |
FAQ-1219 |
Platform: |
Symbian OS v7.0, Symbian OS v7.0s, Symbian OS v8.0, Symbian OS v8.1a, Symbian OS v8.1b |
|
Question: Can I install a MIDlet using a SIS file?
Answer: The MIDP specification provides its own provisioning model based on the Application Descriptor (JAD) and JAR files. In order
to be compliant with the MIDP specification and provide a consistent MIDlet installation experience Symbian OS fully supports
the MIDP provisioning model. Therefore MIDlet developers should present their application in the standard MIDP format of JAR
and JAD file.
In exceptional circumstances, such as when the MIDlet relies on an associated native application to provides additional services
(see FAQ-1198 ) it may be convenient to deliver the entire application bundled as a SIS file. By default the Installer will simply unpack
the SIS file and copy the MIDlet JAR and JAD files to the location in the file system specified in the SIS package file. The
user will then have to navigate to that location using a file browser (if available) and select the JAR or JAD file to complete
the MIDlet installation.
On some platforms (Series 60 for example) it is possible to completely automate this process by use of the FILEMIME (FM)
tag. A sample package file to do this is shown below:
;MyMIDlet.pkg #{"A sample MIDlet"},(0x010000009),1,0,0
;Supports Series 60 2.0 (0x1020216B), 2, 0, 0, {"Series60ProductID"}
"HelloWorld.jad"-"D:\temp\HelloWorld.jad", FM, "text/vnd.sun.j2me.app-descriptor" "HelloWorld.jar"-"D:\temp\HelloWorld.jar"
In this case the Installer unpacks the SIS file, recognizes the JAD MIME type as an installable file, and launches a second
instance of the Installer to complete installation of the MIDlet.
Since the Installer is a licensee customizable component, not all platforms (eg UIQ) support this behaviour.
|
|
|