When deploying the Java Application for the Midp environment a few additional
comments are worth mentioning.
- The developer must use the Midp specific Storage and Communication adapters
(see Using WSDD smart linker) and exclude any classes that are
not Midp compliant.
- You can either use the prepackaged MQeMidp.jar file
or your own reduced version, however a JAD file (Java
application descriptor) must also be included detailing the Midlets available
within the application. When deploying to the device all classes should be
packaged and preverified in one jar before deploying. However, whilst testing
using an emulator several jars can be used by including them in the classpath
- Sun and IBM also provide tools that will generate the required .prc file
for Palm Devices. See documentation within either Sun's Wireless Toolkit or
IBM's WebSphere Studio Device Developer
- Care must be taken to ensure that all the required classes are included
in either the jar/prc file or other executable. Some
classes are dynamically loaded and may be missed when using any Smart-Linker.
See Using WSDD smart linker for more details.