Application Development Using J2ME Evaluation of Maturity and Features

1
Application Development Using J2ME Evaluation
of Maturity and Features
A thesis submitted for the degree of Master of
Science in Information and Communication
Technology
Terje Eggum Håvar Lundberg
2
Evaluation of J2ME

• Hardware access and control
• File access and networking
• General programming issues

3
J2ME on Symbian

• Symbian A mobile operating system
• J2ME A non-native programming language

Symbian OS
Hardware
4
Hardware Control

• Camera and microphone control

Mobile Media API
?
Advanced Multimedia Supplements
5
File Access and Networking

• MMS and SMS

• Wireless Messaging API 1.0

?

• Wireless Messaging API 2.0

• MIDlet Servlet communication

• Access to the file system

• FileConnection API

6
General Programming Issues

• Graphical User Interface
• Generic Connection Framework
• Errors and debugging

7
Overall Evaluation

• Negative aspects Fragmentation Feature support
• Positive aspects Ease of use APIs in development

8
Evaluation of Intrinsic Platform Limitations

• Håvar Lundberg

9
Introduction

• The J2ME Strategy and future application
  development
• Concerns regarding access to new Java APIs

10
The J2ME Strategy and Future Application
Development

• Functionality by using optional packages
• Optional packages and OS support
• Security aspects

11
Security Aspects

• Low level security
• Bytecode verifier
• High level security
• Protocols
• Trusted MIDlets

12
Security Model for Handling Restricted Resources

• High level security
• Trusted MIDlets
• Permissions
• Always, Session,OneShot and Denied
• The user

13
Discussion and Conclusion

• The J2ME Strategy and future application
  development
• J2ME, functionality and the future
• Security aspectsIs the general security
  sufficient?
• Concerns regarding access to new Java APIs
• - Do J2ME handle acces ro restricted APIs in a
  safe manner?

14
Architecture for Device Independence
Terje Eggum
15
Dependency Issues

• Device Design
• Screen
• Input
• Hardware differences
• Operating System
• Fragmented market

16
The J2ME Approach
MIDlet
Optional Packages
MIDP
CLDC
Virtual Machine

• Problems
• Lowest common denominator
• Not all optional packages are supported on every
  device

17
Built In Context Awareness
18
Build On Demand Framework
19
Conclusion

• Framework can help J2ME achieve higher level of
  device independence
• A framework will always be limited by hardware
  differences and API support