JDK 1.3 favicon
All About JDK 1.3
JDK 1.3 • 2000 • Java 1.3
HotSpot JVMJavaSoundRMI-IIOPJava Web Start (beta)Young/Old Gen GC

JDK 1.3 and the shift from JDK 1.2

HotSpot JVM becomes the default. JavaSound, RMI-IIOP, JNDI bundled. Java Web Start beta. Synthetic proxy classes. Performance milestone.

Why JDK 1.3 mattered

The release in context

HotSpot JVM becomes the default. JavaSound, RMI-IIOP, JNDI bundled. Java Web Start beta. Synthetic proxy classes. Performance milestone.

HotSpot JVMJavaSoundRMI-IIOPJava Web Start (beta)Young/Old Gen GC
  • HotSpot JVM becomes the default. JavaSound, RMI-IIOP, JNDI bundled. Java Web Start beta. Synthetic proxy classes. Performance milestone.
  • Key release highlights included HotSpot JVM, JavaSound, RMI-IIOP, Java Web Start (beta).
  • Compared with JDK 1.2, the most visible shifts included Java Web Start (beta), RMI-IIOP, HotSpot JIT (default).
  • HotSpot becomes default JVM. Java performance becomes competitive with C++.
  • The platform posture became less experimental and more dependable for long-lived application servers and enterprise desktop use.
Platform stack

JDK 1.3 architecture preview

This larger diagram expands the smaller JDK badge into a layered platform view showing how the development kit, runtime, virtual machine, APIs, tools, and supporting subsystems fit together for this release.

Previous-version diff

What changed from JDK 1.2 to JDK 1.3

The platform posture became less experimental and more dependable for long-lived application servers and enterprise desktop use.

User Interface Toolkits

  • JavaSound appeared in JDK 1.3, adding a new capability in user interface toolkits.
  • Print Service appeared in JDK 1.3, adding a new capability in user interface toolkits.
  • Swing was updated in JDK 1.3, showing active movement in user interface toolkits.
  • Accessibility carried forward from JDK 1.2 and settled into the baseline by JDK 1.3.

Integration Libraries

  • RMI-IIOP appeared in JDK 1.3, adding a new capability in integration libraries.
  • JNDI (in JRE) was updated in JDK 1.3, showing active movement in integration libraries.
  • RMI was updated in JDK 1.3, showing active movement in integration libraries.
  • IDL carried forward from JDK 1.2 and settled into the baseline by JDK 1.3.

lang and util Base Libraries

  • javax.sound appeared in JDK 1.3, adding a new capability in lang and util base libraries.
  • javax.naming was updated in JDK 1.3, showing active movement in lang and util base libraries.
  • java.lang.reflect moved from active change in JDK 1.2 into a more stable baseline by JDK 1.3.
  • java.security carried forward from JDK 1.2 and settled into the baseline by JDK 1.3.
Matrix slice

Quick comparison table: JDK 1.2 vs JDK 1.3

This side-by-side view turns the source evolution matrix into a faster way to see which language, tooling, runtime, and platform layers moved between these two releases.

Area Component JDK 1.2 JDK 1.3 Why it stands out
Deployment Java Web Start (beta) Not present NEW Java Web Start (beta) appeared in JDK 1.3, adding a new capability in deployment.
Integration Libraries RMI-IIOP Not present NEW RMI-IIOP appeared in JDK 1.3, adding a new capability in integration libraries.
JVM: Execution Engine & GC HotSpot JIT (default) Not present NEW HotSpot JIT (default) appeared in JDK 1.3, adding a new capability in jvm: execution engine & gc.
JVM: Execution Engine & GC Serial GC Not present NEW Serial GC appeared in JDK 1.3, adding a new capability in jvm: execution engine & gc.
JVM: Memory Management Old Gen Not present NEW Old Gen appeared in JDK 1.3, adding a new capability in jvm: memory management.
JVM: Memory Management Young Gen Not present NEW Young Gen appeared in JDK 1.3, adding a new capability in jvm: memory management.
Other Base Libraries Synthetic Proxy Classes Not present NEW Synthetic Proxy Classes appeared in JDK 1.3, adding a new capability in other base libraries.
Tools & Tool APIs HotSpot VM tools Not present NEW HotSpot VM tools appeared in JDK 1.3, adding a new capability in tools & tool apis.
User Interface Toolkits JavaSound Not present NEW JavaSound appeared in JDK 1.3, adding a new capability in user interface toolkits.
User Interface Toolkits Print Service Not present NEW Print Service appeared in JDK 1.3, adding a new capability in user interface toolkits.
lang and util Base Libraries javax.sound Not present NEW javax.sound appeared in JDK 1.3, adding a new capability in lang and util base libraries.
Integration Libraries JNDI (in JRE) Not present UPD JNDI (in JRE) was updated in JDK 1.3, showing active movement in integration libraries.
lang and util Base Libraries javax.naming Not present UPD javax.naming was updated in JDK 1.3, showing active movement in lang and util base libraries.
Java Language Features Reflection Not present Present Reflection appeared in JDK 1.3, adding a new capability in java language features.
Structured comparison

Grouped reading of the release shift

HotSpot becomes default JVM. Java performance becomes competitive with C++.

User Interface Toolkits
New in JDK 1.3
  • JavaSound
  • Print Service
  • Accessibility
  • Drag and Drop
  • Java 2D
Updated by JDK 1.3
  • Swing
Integration Libraries
New in JDK 1.3
  • RMI-IIOP
  • IDL
  • JNDI
Updated by JDK 1.3
  • JNDI (in JRE)
  • RMI
  • JDBC
lang and util Base Libraries
New in JDK 1.3
  • javax.sound
  • java.security
  • java.util.Collections
  • javax.swing
Updated by JDK 1.3
  • javax.naming
  • java.lang.reflect
  • java.util
Historical platform profile

Release narrative

HotSpot JVM becomes the default. JavaSound, RMI-IIOP, JNDI bundled. Java Web Start beta. Synthetic proxy classes. Performance milestone.

HotSpot becomes default JVM. Java performance becomes competitive with C++.

HotSpot JVMJavaSoundRMI-IIOPJava Web Start (beta)Young/Old Gen GC
Why it mattered later

Why JDK 1.3 matters in the JDK timeline

This release fits into the steady JDK cadence where tooling, runtime behavior, and delivery capabilities evolve one step at a time.

  • JDK 1.3 sits in the timeline as a runtime maturity, which shaped how teams evaluated and adopted it.
  • It is commonly remembered for HotSpot JVM, JavaSound, RMI-IIOP.
  • Compared with JDK 1.2, it gives a clearer picture of how the JDK platform was evolving release by release.
  • HotSpot becomes default JVM. Java performance becomes competitive with C++.
Related pages

Continue through the platform story