Girish Mahajan (Editor)

Java Class Library

Updated on
Edit
Like
Comment
Share on FacebookTweet on TwitterShare on LinkedInShare on Reddit

The Java Class Library (JCL) is a set of dynamically loadable libraries that Java applications can call at run time. Because the Java Platform is not dependent on a specific operating system, applications cannot rely on any of the platform-native libraries. Instead, the Java Platform provides a comprehensive set of standard class libraries, containing the functions common to modern operating systems.

Contents

JCL serves three purposes within the Java Platform:

  • Like other standard code libraries, they provide the programmer a well-known set of useful facilities, such as container classes and regular expression processing.
  • The library provides an abstract interface to tasks that would normally depend heavily on the hardware and operating system, such as network access and file access.
  • Some underlying platforms may not support all of the features a Java application expects. In these cases, the library implementation can either emulate those features or provide a consistent way to check for the presence of a specific feature.

    • Implementation and configuration

    JCL is almost entirely written in Java, except for the parts that need direct access to the hardware and operating system (such as for I/O, or bitmap graphics). The classes that give access to these functions commonly use Java Native Interface wrappers to access operating system APIs.

    Almost all of JCL is stored in a single Java archive file called "rt.jar", which is provided with JRE and JDK distributions. The Java Class Library (rt.jar) is located in the default bootstrap classpath, and does not have to appear in the classpath declared for the application. The runtime uses the bootstrap class loader to find the JCL.

    The upcoming Java Module System (planned for Java 9) will break the monolithic "rt.jar" Jar file, and modularize the Java Class Library itself in several modules with specified dependencies.

    Conformance

    Any Java implementation must pass the Java Technology Compatibility Kit tests for compliance, which includes JCL tests.

    Main features

    JCL Features are accessed through classes provided in packages.

  • java.lang contains fundamental classes and interfaces closely tied to the language and runtime system.
  • I/O and networking access the platform file system, and more generally networks through the java.io, java.nio and java.net packages. For networking, SCTP is available through com.sun.nio.sctp.
  • Mathematics package: java.math provides mathematical expressions and evaluation, as well as arbitrary-precision decimal and integer number datatypes.
  • Collections and Utilities : built-in Collection data structures, and utility classes, for Regular expressions, Concurrency, logging and Data compression.
  • GUI and 2D Graphics: the AWT package (java.awt) basic GUI operations and binds to the underlying native system. It also contains the 2D Graphics API. The Swing package (javax.swing) is built on AWT and provides a platform-independent widget toolkit, as well as a Pluggable look and feel. It also deals with editable and non-editable text components.
  • Sound: interfaces and classes for reading, writing, sequencing, and synthesizing of sound data.
  • Text: java.text deals with text, dates, numbers, and messages.
  • Image package: java.awt.image and javax.imageio provide APIs to write, read, and modify images.
  • XML: SAX, DOM, StAX, XSLT transforms, XPath and various APIs for Web services, as SOAP protocol and JAX-WS.
  • CORBA and RMI APIs, including a built-in ORB
  • Security is provided by java.security and encryption services are provided by javax.crypto.
  • Databases: access to SQL databases via java.sql
  • Access to Scripting engines: The javax.script package gives access to any conforming Scripting language.
  • Applets: java.applet allows applications to be downloaded over a network and run within a guarded sandbox
  • Java Beans: java.beans provides ways to manipulate reusable components.
  • Introspection and reflection: java.lang.Class represents a class, but other classes such as Method and Constructor are available in java.lang.reflect.

    • Prior licenses

    Before the release of OpenJDK, the JDK was based on a proprietary license.

    Following their promise to release a fully buildable JDK based almost completely on free and open source code in the first half of 2007, Sun released the complete source code of the Class Library under the GPL on May 8, 2007, except some limited parts that were licensed by Sun from third parties who did not want their code to be released under an open source license. Sun's goal was to replace the parts that remain proprietary and closed source with alternative implementations and make the Class Library completely free and open source.

    Until December 2010, the remaining encumbered part of the JDK was made available by Sun then Oracle as Binary Plugs which were required to build the JDK but not necessary to run it. as of May 2007, the only part of the Class library that remained proprietary and closed-source (4% as of May 2007 for OpenJDK 7, and less than 1% as of May 2008 and OpenJDK 6) was:

  • The SNMP implementation.

    • Since the first May 2007 release, Sun, with the help of the community, released as open source or replaced with open source alternatives almost all the encumbered code:

  • All the audio engine code, including the software synthesizer, became open source. The closed-source software synthesizer has been replaced by a new synthesizer developed specifically for OpenJDK called Gervill,
  • All cryptography classes were released as open source,
  • The code that scales and rasterizes fonts uses open source FreeType
  • The native color management uses open source LittleCMS. There is a pluggable layer in the JDK, so that the commercial release of Java can use the original, proprietary color management system and OpenJDK can use LittleCMS.
  • The anti-aliasing graphics rasterizer code uses the open source Pisces renderer used in the phoneME project.
  • The JavaScript plugin is open source (the JavaScript engine itself was open source from the beginning).

    • Open source release

    Beginning in December 2010, all the so-called binary plugs were replaced by open source replacements, making the entire JDK open.

    Alternative implementations

    GNU Classpath is the other main free software class library for Java. Contrary to other implementations, it only implements the Class Library, and is used by many free Java runtimes (like Kaffe, SableVM, JamVM, CACAO).

    Apache Harmony was another free software class library. Its aim was to implement the other parts of the Java stack (Virtual Machine, Compiler, and other tools required for any Java implementation).

    References

    Java Class Library Wikipedia
    (Text) CC BY-SA