< Previous PageNext Page > Hide TOC

Resolved Issues Since Java 1.4.1

The issues discussed here represent specific bugs that have been fixed since the Java 1.4.1 release. This listing is not a complete list of bugs that have been fixed, but a snapshot of issues that might be of interest.

Each issue is broken down as follows:

In this section:

Java Aqua Look and Feel
Java AWT
Java Graphics
Java Plugin
Java Web Start


Java Aqua Look and Feel

Radar #3166127

JOptionPane dialog buttons have mnemonics.

Description:

JOptionPane.showConfirmDialog displays Yes and No with an underscore under the Y and the N. These underscores should not be visible with the Aqua look and Feel.

Resolution:

None.

Java AWT

Radar #3114971

Memory/address space leak when creating & disposing java.awt.Window objects.

Description:

There had been memory and address space leaks noticed when creating and disposing java.awt.Window objects.

Resolution:

This has been fixed.

Radar #3230598

JAWT shouldn't provide a QuickDraw Port.

Description:

JAWT's bindings have been changed to provide the actual Cocoa view for the AWT component being rendered to.

Resolution:

This has been fixed.

Radar #3201008

Failing to draw window grow boxes.

Description:

Grow boxes once again draw in the lower-right. In the previous release they did not.

Resolution:

This has been fixed.

Radar #3216572

Java 1.4.1 must bump mrj.version automatically.

Description:

Make mrj.version property increment automatically.

java version "1.4.1_01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-62)
Java HotSpot(TM) Client VM (build 1.4.1_01-22, mixed mode)
mrj.version is "62".
Resolution:

This has been fixed. For long-term cross platform usage, developers should use the java property “java.runtime.version” which in the above case is "1.4.1_01-62". This (along with “os.version”) are the cross platform properties to check.

Radar #3222044

In the Java 1.4.1 release, Java used memory and did not always dispose of that memory.

Description:

Java 1.4.1 Update 1 is much better at recovering used memory. Previous seeds may have crashed during attempts to access stale resources that had been disposed of—that category of crash is fixed in the final release.

Resolution:

This has been fixed.

Java Graphics

Radar #3257398

Need debug code for rendering primitives.

Description:

This new debugging mechanism lets you control which graphics primitives should be rendered and which should not. By default all are rendered. One task this enables is to see how certain graphics primitives affect an application’s performance.

Resolution:

This has been fixed.

Java Plugin

Radar #3198591

Problem with putting applet certificate in keystore on Java 1.4.1.

Description:

Self-signed certificates generated in Java 1.1 and earlier can now be stored in the keychain.

Workaround:

This has been fixed.

Java Web Start

Radar #3183878

Web Start-based double-clickables always get 1.3.1.

Description:

Java Web Start applications now work with Java 1.4.1. In the previous release, Java Web Start applications did not add the JVMVersion key in the Java dictionary, so they always used Java 1.3.1.

Resolution:

This has been fixed. If this problem was affecting your applications, you will need to discard and re-create any affected application.



< Previous PageNext Page > Hide TOC


© 2003 Apple Computer, Inc. All Rights Reserved. (Last updated: 2003-09-02)


Did this document help you?
Yes: Tell us what works for you.
It’s good, but: Report typos, inaccuracies, and so forth.
It wasn’t helpful: Tell us what would have helped.