By writing to the Java platform, developers and content providers can ensure that their applications are more portable, but applications that take advantage of extremely specialized options on one device are naturally limited in their portability. Another very important goal was ensuring reuse of existing APIs, and the rational subsetting of existing APIs. Naturally, we didn't want to see five different GUI APIs appearing. An API exposing a specific functionality. Includes a list of API dependencies and must be deployed with a profile that supports the dependencies.
Optional packages can reference existing or new APIs and other optional packages.
The minimum-sized, preexisting profile defined for the specific VM that it is deployed against. CLDC, MIDP, CDC, and the Foundation Profile have already been approved, with specifications for RMI, Bluetooth, new media APIs, and others still in development through the JCP program. This JSR addresses questions of how to develop applications using the J2EE TM platform and then how to deploy those applications to the existing devices. If you're talking about deploying devices right now, you can also go straight to the PersonalJava TM platform, which runs on a wide variety of devices today. Inc. All Rights Reserved.