Editing Connected Limited Device Configuration (section)

==Noteworthy limitations==
Compared to the [[Java SE]] environment, several APIs are absent entirely, and some APIs are altered such that code requires explicit changes to support CLDC. In particular, certain changes are not just the absence of classes or interfaces, but actually change the signatures of existing classes in the base class library. An example of this is the absence of the <code>Serializable</code> interface, which does not appear in the base class library due to restrictions on reflection usage. All <code>java.lang.*</code> classes which normally implement <code>Serializable</code> do not, therefore, implement this [[Marker interface pattern|tagging interface]].

Other examples of limitations depend on the version being used, as some features were re-introduced with version 1.1 of CLDC.<ref>J2ME APIs: Which APIs come from the J2SE Platform? http://developers.sun.com/mobility/midp/articles/api/</ref>

===CLDC 1.0 and 1.1===
* The <code>Serializable</code> interface is not supported.
* Parts of the reflection capabilities of the Java standard edition:
** The <code>[http://java.sun.com/javase/6/docs/api/java/lang/reflect/package-summary.html java.lang.reflect]</code> [[Java package|package]] and any of its classes not supported.
** Methods on <code>[http://java.sun.com/javase/6/docs/api/java/lang/Class.html java.lang.Class]</code> which obtain Constructors or Methods or Fields.
* No finalization. CLDC does not include the <code>Object.finalize()</code> method.
* Limited error handling. Non-runtime errors are handled by terminating the application or resetting the device.
* No user-defined class loaders
* No thread groups or daemon threads.