Invoking applications in Java ME

MIDP 2.1 compliant devices support the javax.microedition.MIDlet classes completely as defined in the MIDP 2.1 JSR. The text below lists additional implementation information for this package.

It is recommended to implement MIDlets in a way that ensures that the startApp and destroyApp methods return quickly.

For example, if the MIDlet startup requires several time-consuming initializations, it is recommended to do the startup in a separate thread so that the startApp returns quickly.

platformRequest

Return value of platformRequest is always false , as the request is executed immediately. The return value indicates that the calling MIDlet does not need to exit for the object to run.

Table: Supported URI schemes:

URI scheme

Supported in Series 40 and Nokia Asha software platform devices

Java user confirmation prompt on Nokia Asha software platform 1.0 devices

Java user confirmation prompt on Series 40

Behavior

http:

Yes

No user prompt. Launches the browser

"Allow this application to use network for sending/receiving data?"

Open URI in Browser

https:

Yes

No user prompt. Launches the browser

"Allow this application to use network for sending/receiving data?"

Open URI in Browser

rtsp:

Product dependent

Not supported

"Allow this application to use network for sending/receiving data?"

Open URI in RealPlayer

tel:

Yes

No user prompt. Displays a screen with the telephone number from which the user can either tap to call or add the number to the contacts.

No user prompt

Asks confirmation before making phone call

mailto:

Product dependent

No user prompt. Launches the Mail native application. If a valid mail account has been set up, the recipient’s address is filled with the mailto value.

No user prompt

Open E-mail or MMS editor

file:

On Asha software platform only

 

No user prompt

Open file in MIME type specific application

The 'Allow this application start an application?' prompts resulting from calling the platformRequest method are independent from other possible prompts in the MIDP runtime.

For http: and https: schemes prompt is shown for trusted third party and untrusted MIDlets on Series 40 devices. Also a browser confirmation prompt can be shown. On Nokia Asha software platform devices, these schemes do not generate any prompts, in either the untrusted 3rd party or trusted 3rd party domains.

Note: After closing the handler application or pressing the back key on Nokia Asha software platform devices, the MIDlet is brought to the foreground.

Concurrency

Series 40 and Nokia Asha software platform devices allow running of the MIDlet and the handler application concurrently, so there is no need to terminate the MIDlet, except when installing a new version.

Platform requests are executed immediately, they are not queued.

Examples

Making a phone call:

platformRequest("tel:+19123456789"); 

Opening a web page:

platformRequest("http://www.developer.nokia.com/"); 

Opening an RTSP streaming connection:

platformRequest("rtsp://ra.yle.fi/ramgen/tv2/viihde/zencafe.rm"); 

Opening a local file with default handler application:

platformRequest("file:///MemoryCard/image.png"); 

Opening SMS editor for sending SMS to a specified telephone number:

platformRequest("sms:+19123456789"); 

A Nokia Developer use case that contains the complete source code of a sample MIDlet that makes a platform request: Code snippet of phone call.