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

Debugging with the MDS simulator


The MDS simulator is an important piece of the debugging puzzle. So far, you have used only the Direct TCP/IP transport in the examples that you've done. While this is the easiest to do during development and testing, it is not necessarily the best transport to use in production. It's good to use in testing because there are fewer components involved and therefore, fewer points of failure. If you can't get it to work by using Direct TCP/IP in the simulator, you most likely won't be able to get it to work using any other transports.

If you recall, using the MDS transport provides an encrypted and secure tunnel for the networking communication to travel through between your handheld to your server in your office. The MDS simulator provides that same secured tunnel between the simulator and your local machine so that you can test applications that use that tunnel.

The browser application on the simulator uses the MDS transport, which is why you can't use the browser...