The JavaClass Library 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. JCL serves three purposes within the Java Platform:
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
Java Class Library is almost entirely written in Java, except for the parts that need direct access to the hardware and operating system. 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 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 Java Module System broke the monolithic "rt.jar" JAR file and modularized the JCL itself in several modules with specified dependencies.
GUI and 2D Graphics: the AWT package basic GUI operations and binds to the underlying native system. It also contains the 2D GraphicsAPI. The Swing package 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: deals with text, dates, numbers and messages.
Image package: and provide APIs to write, read, and modify images.
Access to Scripting engines: The package gives access to any conforming Scripting language.
Applets: allows applications to be downloaded over a network and run within a guarded sandbox
Java Beans: provides ways to manipulate reusable components.
Introspection and reflection: represents a class, but other classes such as Method and Constructor are available in.
Licensing
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 on almost completely 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 2007, the only part of the Class library that remained proprietary and closed-source was:
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 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.
Beginning in December 2010, all the so-called binary plugs were replaced by open source replacements, making the entire JDK open.
Alternative implementations
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. Apache Harmony was another free software class library. Its aim was to implement the other parts of the Java stack .
