Book Image

BlackBerry Java Application Development

Book Image

BlackBerry Java Application Development

Overview of this book

BlackBerry Smartphone was once the domain of jet-setting business users with power suits. Now you can hardly go anywhere without seeing someone using a BlackBerry to check their messages or make a call. It's this kind of explosive growth that makes the BlackBerry ecosystem a great place to develop and market applications through the BlackBerry App World store—this book shows you how to do just that! This step-by-step guide gives you a hands-on experience of developing innovative Java applications for your BlackBerry. With the help of this book, you will learn to build your own applications to illustrate the platform, and the various capabilities that developers can use in their programs. It explores the powers of Blackberry and helps you develop professional and impressive Java applications. The book teaches how to write rich, interactive, and smart BlackBerry applications in Java. It expects the readers to know Java but not Java Mobile or the BlackBerry APIs. We will learn to build rich, interactive, and smart Java applications for the BlackBerry. The book will cover UI programming, data storage, programming network, and internet API apps. As we move on, we will learn more about the BlackBerry's device features, such as messaging, GPS, multimedia, contacts and calendar, and so on.This book also helps you build your own applications to illustrate the platform, and the various capabilities that developers can use in their programs.
Table of Contents (18 chapters)
BlackBerry Java Application Development
Credits
About the Author
Acknowledgement
About the Reviewers
Preface

The BlackBerry way: Persistent Store


As we said before, RMS is the storage method provided with Java. Like most of the Java SDK there are BlackBerry-specific alternatives available and, in general, these should be used unless you are trying to create a true MIDlet. When it comes to database storage the BlackBerry-specific alternative is called the Persistent Store.

  • Easier to code: Using the PersistentStore approach is generally easier than RMS because PersistentStore provides a generic serialization mechanism allowing you to store complex objects in it. This means that the special code you made for the load and save methods are not needed. There are several factors that should be considered before choosing to use either PersistentStore or RMS

  • Must implement Persistable interface: In order to store custom data classes in PersistentStore they must implement the Persistable interface. Implementing this interface serves as a flag to the PersistentStore object that the class is intended to be stored...