javax.swing

javax.swing
GPL · source
Name	javax.swing
Author	Sun Microsystems
Introduced	1997
Language	Java
License	Oracle Binary Code License

javax.swing

javax.swing is a Java library that provides a rich set of graphical user interface widgets for building desktop applications on the Java Platform, Standard Edition. It complements the Abstract Window Toolkit and integrates with the Java Runtime Environment, enabling developers working with the Java Class Library, Oracle, and OpenJDK to create cross-platform user interfaces for projects used by organizations such as IBM, Google, Microsoft, and Apache. Swing components are widely deployed in enterprise applications at companies like Red Hat, SAP, VMware, and in scientific tools developed at institutions such as MIT, Stanford, and CERN.

Overview

javax.swing supplies a hierarchy of lightweight components that replace or augment heavy-weight peers from AWT for applications running on platforms like Windows, macOS, and Linux. Major contributors and stakeholders in its design included Sun Microsystems engineers, Oracle developers, and open source communities centered on the OpenJDK project, with adoption by corporations such as IBM, Oracle Corporation, and Hewlett-Packard. The toolkit influenced graphical toolkits in environments like GNOME and KDE and interoperates with technologies from projects such as Apache Ant, Maven, and Jenkins, which often build and deploy Swing-based administration consoles.

Components and Architecture

The package organizes components into classes such as JButton, JLabel, JTable, and JTree, implemented as part of the Java Class Library maintained by Oracle and OpenJDK contributors. Architectural decisions were informed by designers influenced by Smalltalk and frameworks in research at Xerox PARC and universities including Carnegie Mellon and UC Berkeley. Swing's lightweight component model contrasts with AWT and shares conceptual lineage with GUI frameworks like Qt from Nokia, GTK from Red Hat, and Cocoa from Apple. Development tools such as NetBeans, Eclipse, and IntelliJ IDEA include visual editors that generate code using Swing classes and layout managers like BorderLayout, GridBagLayout, and BoxLayout.

Event Handling and MVC Pattern

Event delivery in Swing follows a model that integrates concepts from the Model–View–Controller pattern pioneered in desktop research at Xerox PARC and refined in systems from IBM and DEC. Swing separates state and representation through model classes used by components such as JTable's TableModel and JList's ListModel, reminiscent of design patterns taught at Stanford and Harvard and used in projects at NASA and the European Space Agency. Event listeners and adapters implement callback patterns similar to those in frameworks such as .NET from Microsoft and GTK's signal system maintained by contributors from Red Hat and Canonical.

Look and Feel and Pluggable UI

Swing supports a pluggable Look and Feel architecture allowing skins inspired by native platforms like Windows NT, macOS Aqua, and GNOME’s Adwaita, as well as third-party themes developed by companies like JetBrains and community projects hosted on GitHub. PluggableUI implementations and UI delegates enable customization akin to theming engines in KDE and Firefox, and have been used in commercial products from Oracle, IBM, and SAP. The Synth framework and Metal theme originated at Sun Microsystems and were extended by designers from companies such as Sun, Oracle, and Azul Systems.

Threading and Concurrency (EDT)

Swing mandates that most GUI updates occur on the Event Dispatch Thread, a design influenced by concurrency models studied at MIT's Laboratory for Computer Science and by multithreading practices in platforms like Microsoft Windows and POSIX systems. Utilities such as SwingUtilities.invokeLater and SwingWorker were added to simplify background processing for long-running tasks found in applications developed by NASA, CERN, and large banks including JPMorgan Chase and Goldman Sachs. Proper EDT usage is critical in enterprise projects using frameworks like Spring, Jakarta EE, and Hibernate when integrating Swing-based admin tools.

Common Components and Containers

Common containers and components include JFrame, JPanel, JDialog, JMenuBar, JToolBar, JScrollPane, JTable, JComboBox, and JTree, used extensively in applications produced by companies such as Adobe, IBM, Oracle, and VMware. Swing integrates with printing APIs and accessibility technologies mandated by standards bodies and implemented by assistive technology vendors like Freedom Scientific and Apple. Complex components have driven innovations reused in IDEs such as NetBeans, IntelliJ IDEA, and Eclipse RCP, and in tools from Autodesk and Siemens.

History and Evolution

Swing emerged at Sun Microsystems in the late 1990s as part of efforts led by engineers who also worked on HotSpot and the Java language, during a period featuring contemporaneous releases such as Java 1.2 and projects like JDK 1.2 (codename Starfire). Over time, stewardship moved through Oracle after the Sun acquisition and into OpenJDK governance with contributions from companies like Red Hat, Azul Systems, and IBM. Swing's evolution intersects with industry events such as the rise of web architectures promoted by Microsoft and Google, and the subsequent growth of JavaFX as a successor in some use cases, while Swing remains maintained for legacy, scientific, and enterprise desktop applications at institutions including CERN, NASA, and major financial firms.

Category:Java libraries