Java Reference
In-Depth Information
Basis Profile, the profile does
not
support RMI; just enough of the RMI implementation is
included to facilitate communication between two Xlets running on the same device.
Introducing the Personal Profile
The Personal Profile is a superset of the Personal Basis Profile that provides support
for the entire AWT, as well as limited JavaBean support. Some readers may remember
PersonalJava, the predecessor to Java ME that was targeted for higher-end Internet
appliances and set-top boxes; the Personal Profile atop the CDC is the forward migra-
tion path for applications running on PersonalJava.
In fact, the Personal Profile is almost the same as Java SE 1.4.2, with these differences:
• Support for RMI is available through an optional package (
java.rmi
).
• Support for SQL is available through an optional package (
java.sql
).
• Support for Java Swing is available through an optional package (
java.swing
).
• Support for Object Management Group (OMG) interfaces, including Common
Object Request Broker Architecture (CORBA), is available through an optional
package (
org.omg
).
• There is no support at present for the Java Accessibility API (
javax.accessibility
).
• There is no support at present for the Java Naming and Directory Interface ( JNDI)
in
java.naming
.
• There is no support for the Java Sound API (
java.sound
).
• Support for JavaBeans is limited to runtime support; there is no support for bean
editors running directly on a CDC environment.
• The applet API
getAccessibleContext
is not supported.
• Applet and AWT methods deprecated from Java SE have been removed from all
supported classes.
Understanding Packages
A package, as its name implies, is an object or group of objects in a common container.
As important as platforms and profiles are to the modularity of the Java ME platform,
packages are arguably the key to Java ME's continued success, as they permit Sun and
third-party vendors to extend the Java ME platform for specific families of devices.
