Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries over the next few weeks. Thanks for all your past and future contributions.


From Wiki
Jump to: navigation, search
Article Metadata
Created: firt (01 Apr 2007)
Last edited: hamishwillee (24 Jul 2013)



The Connected Limited Device Configuration (CLDC) defines the base set of application programming interfaces and a virtual machine for resource-constrained devices like mobile phones in Java ME.

Over CLDC usually exists MIDP 1.0 or MIDP 2.0. It was developed under the Java Community Process as JSR 30 (CLDC 1.0) and JSR 139 (CLDC 1.1).

The Virtual Machine installed on the phone for this configuration usually has 100-160Kb.


CLDC 1.0 did not support any form of floating point arithmetic (float or double Java types). This limitation was removed in CLDC 1.1.

See How to use floating point numbers in CLDC 1.0

Packages included

  • java.lang
  • java.util

Difference between CLDC 1.0 and CLDC 1.1

The list below summarizes the main differences between CLDC Specification versions 1.1 (JSR-139) and 1.0 (JSR-30):

  1. Floating point support.
    • All floating point byte codes are supported by CLDC 1.1.
    • Classes Float and Double have been added.
    • Various methods have been added to the other library classes to handle floating point values.
  2. Weak reference support (small subset of the J2SE weak reference classes.)
  3. Redesigned, more J2SE-compliant Calendar/Date/TimeZone classes.
  4. Error handling requirements have been clarified, and one new error class, NoClassDefFoundError, has been added.
  5. Various minor library changes and bug fixes, such as the addition of the following fields and methods:
    • Boolean.TRUE and Boolean.FALSE
    • String.intern()
    • Date.toString()
    • Random.nextInt(int n)
  6. Minimum memory budget raised from 160 to 192 kilobytes, mainly because of the added floating point functionality.
  7. Specification text tightened and obsolete subsections removed.
  8. Much more detailed verifier specification ("CLDC Byte Code Typechecker Specification") is provided as an appendix.


This page was last modified on 24 July 2013, at 06:22.
82 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.


Thank you!

We appreciate your feedback.