Sun Microsystems J2ME User Manual Page 116
- Page / 134
- Table of contents
- BOOKMARKS
Rated. / 5. Based on customer reviews
104 J2ME Wireless Toolkit User’s Guide • October 2004
B.2.1 Build
Using KToolbar, building a project is a single step. Behind the scenes, however,
there are actually two steps. First, Java source files are compiled into Java class
files. Next, the class files are preverified, which means they are prepared for the
CLDC KVM.
Use the javac compiler from the J2SE SDK to compile Java source files. You can
use the existing J2ME Wireless Toolkit project directory structure. You’ll need to
use the -bootclasspath option to tell the compiler to use the MIDP APIs, and
you’ll use the -d option to tell the compiler where to put the compiled class files.
The following example shows how you could compile a MIDP 2.0 application,
taking source files from the src directory and placing the class files in the
tmpclasses directory. Newlines have been added for clarity.
javac
-bootclasspath ..\..\lib\cldcapi10.jar;..\..\lib\midpapi20.jar
-d tmpclasses
src\*.java
If you want to use the optional APIs that are supported by the toolkit, add their
JAR files to the -bootclasspath option.
For more information on javac, consult the J2SE documentation.
The next step is to preverify the class files. In the bin directory of the J2ME
Wireless Toolkit lives a handy utility called preverify. The syntax for the
preverify command is as follows:
preverify [options] <files | directories>
Some of the options are as follows:
-classpath <classpath>
Specify the directories or JAR files (given as a semicolon-delimited list) from
which classes are loaded.
-d <output directory>
Specify the directory into which the preverifier should output classes. This
directory must exist before preverifying. If this option is not used, the preverifier
places the classes in a directory called output.
Following the example for compiling, use the following command to verify the
compiled class files. As before, newlines have been added for clarity.
preverify
-classpath ..\..\lib\cldcapi10.jar;..\..\lib\midpapi20.jar
-d classes
tmpclasses
- User’s Guide 1
- Contents 3
- Contents v 5
- Contents vii 7
- Index 119 8
- Who Should Use This Book 9
- Related Documentation 9
- How This Book Is Organized 10
- Preface xi 11
- Typographic Conventions 12
- We Welcome Your Comments 12
- Introduction 13
- 1.2 The Tools in the Toolkit 14
- 1.3 Toolkit Features 15
- 1.4 Supported Technology 15
- Developing MIDlet Suites 17
- The KToolbar window 18
- Creating a new project 18
- 2.2.1 Edit Source Code 19
- 2.2.2 Build 20
- 2.2.3 Run 21
- List of project MIDlets 22
- TinyMIDlet in action 22
- 2.3.1 Package 23
- 2.3.2 Install 24
- URL prompt 25
- Confirming the installation 25
- 2.3.3 Run 26
- 2.4 Using an Obfuscator 27
- 2.5 Using a Debugger 29
- ■ From the command line, run: 30
- The project settings window 32
- 3.3 Manipulating MIDlets 35
- 3.4 Using the Push Registry 36
- Project directory structure 37
- 3.7 Configuring KToolbar 38
- Using the Emulator 41
- 4.2 Using the Emulator 42
- 4.3.1 Network Proxies 44
- 4.3.2 Heap Size 45
- 4.3.3 Storage and Cleaning 45
- 4.4 Pausing and Resuming 47
- 4.5 Running the Emulator Solo 48
- Monitoring Applications 51
- Turning on the profiler 52
- The method profiler 52
- 5.1.1 The Call Graph 53
- 5.2 Using the Memory Monitor 54
- 5.3 Using the Network Monitor 56
- 5.3.1 Filtering Messages 57
- 5.3.2 Sorting Messages 58
- Information 58
- Security and MIDlet Signing 61
- 6.2 Protection Domains 62
- 6.3 Signing a MIDlet Suite 63
- 6.4 Managing Keys 64
- 6.4.2 Getting Real Keys 65
- 6.5 Managing Certificates 66
- 6.5.1 Importing Certificates 67
- 6.5.2 Removing Certificates 68
- Setting WMA preferences 70
- The WMA console 71
- Sending a binary message 73
- 7.3.4 Sending MMS Messages 74
- Using the Mobile Media API 77
- 8.2 Using MediaControlSkin 78
- 8.3 Media Capture 78
- 8.4 Well-Behaved MIDlets 78
- 9.1 JSR 184 Overview 79
- 9.2 Immediate Mode 79
- 9.4 Trading Quality for Speed 80
- 9.3 Retained Mode 80
- 10.1 The FileConnection API 83
- 10.2 The PIM API 84
- Using the Bluetooth and OBEX 85
- 11.3.1 OBEX Preferences 86
- BCC properties 87
- Using Web Services 89
- Application Demonstrations 91
- WMADemo is contained in 92
- A.2 General Instructions 93
- A.3 BluetoothDemo 94
- A.4 Demo3D 96
- A.4.2 PogoRoo 97
- A.4.3 retainedmode 98
- A.5 JSR172Demo 99
- A.6 mmademo 99
- A.6.1 Simple Tones 100
- A.6.2 Simple Player 100
- Simple Player commands 101
- A.6.3 PausingAudioTest 102
- A.6.4 Video 102
- A.7 ObexDemo 103
- A.8 PDAPDemo 106
- A.8.2 The PIM API 108
- An empty contact list 109
- Adding contact fields 109
- A.9 WMADemo 110
- Sending a text message 111
- An incoming text message 112
- Addressing an MMS message 113
- WMADemo receives the image 114
- Command Line Reference 115
- B.2.1 Build 116
- B.2.2 Package 117
- B.2.3 Run 118
- B.2.4 Debugging 119
- Toolkit component commands 120
- B.5 Using Security Features 122
- B.5.2 Signing MIDlet Suites 123
- B.5.3 Managing Certificates 124
- B.6 Using the Stub Generator 125
- B.6.1.1 Example 126
- Internationalization 127
- C.2 Emulated Locale 128
- C.3 Character Encodings 128
- Index 121 133
Related products and manuals for Software manuals Sun Microsystems J2ME
(256 pages)
(50 pages)© 2020, manymanuals.com. All rights reserved. | 0.944 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comments to this Manuals