• JSRs by Platform
• JSRs by Technology
• JSRs by Stage
• JSRs by Committee
• List of All JSRs



Register for Site

Use of JCP site is subject to the JCP Terms of Use and the Oracle Privacy Policy


• About JCP
  • Program Overview
  • JCP Process Document
  • Calendar
  • JCP Members
  • Executive Committee
  • Elections
• Get Involved
  • Overview
  • Becoming a JCP Member
  • Java in Education
• Community Resources
  • Overview
  • Tutorials
  • JCP Podcasts
  • Spec Lead Guide
  • TCK Tool & Info
  • License Reference
• Community News
  • News
  • Programs & Awards
  • Press Releases
  • Success Stories
• FAQ
• Contact Us

API Specification Clarifications in J2SE^TM 1.3.1

No signature changes

J2SE 1.3.1 contains no changes to the API specifictation at the signature level. There are no changes to the signatures of any class or method, nor are there any new classes or class members in the J2SE 1.3.1 specification.

No Impact to Java Compatibility Kit

The J2SE 1.3.1 specification does not require a new Java Compatibility Kit (JCK). The JCK used for J2SE 1.3.0 applies also to J2SE 1.3.1.

Clarifications

The wording of the API specification has been amended in some places to clarify behavior. Many of these clarifications have been made in response to bug reports and requests submitted by our partners and J2SE users. In no case does the wording of the clarifications impact the JCK test suite.

The J2SE 1.3.1 specification contains clarifications to approximately 90 class members, counting clarifications to class-level and package-level specifications.

View the Clarifications

All J2SE 1.3.1 specification clarifications are viewable in the form of HTML differences to the Javadoc output. Download the archived Difference Pages.