This document summarizes a presentation on developing and testing Java mobile applications across different devices. It discusses developing a simple application to perform network connections and store response codes, testing it using emulators and tools, and then deploying it to actual devices like the Sharp GX20, Nokia 6630, and Motorola V980. It finds issues like RMS storage limitations and attribute naming issues that require changes to make the application work across all devices tested. The key takeaway is that the "Write Once, Test Anywhere, Work Around" paradigm is important for Java mobile development.

1. Java Mobile Developers Forum
Deploy and test a
simple application
using actual devices
Edoardo Schepis
edoardo.schepis@sun.com
Milano - 23 Settembre 2005

2. Java Mobile Developers Forum
Developing the FragmentationDemo
• Main requirement: a simple MIDlet performing network
connections
>HTTP
>HTTPS
• Store HTTP/S response codes in RMS
• UI
Tools
> a form for user interactions reporting NetBeans 4.1 + Mobility
●
events Pack
Sun Wireless Toolkit
●
• Configuration Nokia Developer Suite
●
> in JAD file Motorola SDK
●
● SonyEricsson Toolkit
23 Settembre 2005

3. Java Mobile Developers Forum
NetBeans Mobility Pack
Flow Designer
23 Settembre 2005

4. Java Mobile Developers Forum
NetBeans Mobility Pack
Screen Designer
23 Settembre 2005

5. Java Mobile Developers Forum
NetBeans Mobility Pack
MIDlet
Attributes
23 Settembre 2005

6. Java Mobile Developers Forum
Java Source
public class FrDemoMIDlet extends MIDlet implements CommandListener {
....
public FrDemoMIDlet() {
URL = this.getAppProperty("host.URL");
http_port = this.getAppProperty("host.http_port");
https_port = this.getAppProperty("host.https_port");
}
....
void doHttpConnect() {
HttpConnection httpConnection = null;
connectionURL = "http://" + URL + ":" + http_port;
mainForm.append("Connecting to..." + connectionURL);
try {
httpConnection = (HttpConnection) Connector.open(connectionURL);
int httpResponseCode = httpConnection.getResponseCode();
mainForm.append("HTTP ResponseCode: " + httpResponseCode);
recordstore.addRecord(new byte[] {(new Integer(httpResponseCode)).byteValue()}, 0,
0);
} catch (IOException e) { ....
23 Settembre 2005

7. Java Mobile Developers Forum
Testing with emulators
● OTA provisioning
● Main functions
– Reading from JAD file
– User interactions
– Network connections
– RMS
23 Settembre 2005

8. Java Mobile Developers Forum
Now let's use devices...
The simple application should follow the W.O.R.A.
paradigm
23 Settembre 2005

9. Java Mobile Developers Forum
Handsets
• Sharp GX20
• Nokia 6630
• Motorola V980
• SonyEricsson P910
23 Settembre 2005

10. Java Mobile Developers Forum
Live demo with Sharp GX20
23 Settembre 2005

11. Java Mobile Developers Forum
Testing Results Summary
Device Provisioning Execution Issue Solution
MIDlet-Data_Size+
Sharp GX20 OK KO RMS / no https
change app.
KO
Nokia 6630 - Attribute Name with '.' Change Names
(version 2.xy)
Motorola V980 OK KO HTTP and Thread Separate Thread
SE P910 OK KO User Interface Re-Design UI
Note:
not only bugs... but also
specific implementations
23 Settembre 2005

12. Java Mobile Developers Forum
Java Devices EchoSystem
23 Settembre 2005

13. Java Mobile Developers Forum
If I had to remember one thing...
“Write Once, Test Anywhere,
Work Around”
23 Settembre 2005

14. Edoardo Schepis
edoardo.schepis@sun.com