< Previous PageNext Page > Hide TOC

Resolved Issues

This chapter lists high-visibility bugs that have been addressed in this release. It is not a complete listing of all of the bugs addressed. If you still have issues with any of these bugs, please file a new bug at http://bugreport.apple.com/ under the Java (new bugs) component, Version X. Refer to the bug number indicated below in your new bug if you believe it is the same issue.

In this section:

Java AWT
Java Events
Java Graphics
Java HotSpot
Java Plugin
Java Security


Java AWT

Radar #3065640

Drag action modifier key issues.

Description:

There were serveral issues caused by some fundamental mismatches between the Mac OS X drag-and-drop system and the Java drag-and-drop system:

Resolution:

All of the above have now been fixed. The current drag action modifier key behavior is detailed in Table 2-1:

Table 1-1  Drag action modifier key behavior

Modifier Style

Copy

Move

Link

Behavior

Java

Control

Shift

Control+Shift

Within and between Java applications; from native applications to Java applications.

Mac OS X

Option

Command

Command+Option

Within and between Java applications; between native and Java applications.

If you want to determine which action is taking place regardless of the modifier style used, check for ACTION_COPY, ACTION_LINK, and ACTION_MOVE using DragSourceDragEvent.getUserAction().

Radar #3550815

Image background color problems.

Description:

Images would display with a black background.

Resolution:

Images are now contained within components and use the component's background color when drawing.

Radar #3578909

AWT component issues.

Description:

Every time a heavyweight AWT component was added to a container, it would validate and lay out the container.

Resolution:

Adding a component no longer forces the container to validate and lay itself out.

Radar #3730358

Font style changes to Italic and Italic & Bold do not work for Dialog and Serif mode.

Description:

Microsoft Office installs fonts into ~/Library/Fonts/. Once installed, these fonts are used by Java applications instead of those installed with the system. This causes problems with the standard Dialog and Serif fonts, Arial and Times New Roman.

Resolution:

When conflicting fonts are present, the system-installed copies are used.

Java Events

Radar #2669001

Element dragging displays an oddly-shaped outline.

Description:

Dragging a JList, JTable, or JTree element causes an outline much larger than the element to be displayed during the drag.

Resolution:

Dragging an element now outlines just the element.

Radar #3550412

Right-button drag-and-drop operations disable all further drag-and-drop operations.

Description:

Mac OS X does not support right-button drag-and-drop operations. This caused an ASSERT and disabled all drag-and-drop operations for a Java application.

Resolution:

A right-button drag-and-drop operation no longer causes an ASSERT. Note that right-button drag-and-drop behavior is still unsupported.

Radar #3571921

DropTargets fail to register as valid.

Description:

Sometimes a DropTarget failed to register, causing drag-and-drop operations to fail.

Resolution:

All DropTarget components now register properly.

Radar #3593460

Non-serializable objects could not be dragged.

Description:

In some cases, non-serializable objects could not be dragged within an application because they were not properly registered with the Mac OS X drag-and-drop system.

Resolution:

Non-serializable objects can now be dragged within an application.

Radar #3607770

Drag-and-drop coordinate system issues.

Description:

During drag-and-drop, a DragSourceListener can be registered to receive notifications about the progress of the drag operation. The notifications contain events that can be queried for the location of the mouse cursor at the time of the event. Previously, you were supplied with the cursor location in window-relative coordinates, even though Java specifies that the cursor location be supplied in screen coordinates.

Resolution:

The mouse cursor location is now returned in screen coordinates.

Java Graphics

Radar #3481676

Full screen mode support.

Description:

Full screen mode was problematic and frequently caused issues.

Resolution:

Full screen mode now functions as expected.

Java HotSpot

Radar #3569904

Long variables and the PowerPC G5.

Description:

Long variables could be put into an unknown state when running a Java application on a G5-equipped machine.

Resolution:

Long variables are now properly handled.

Radar #3644530

MaxPermSize increased.

Description:

Server Java applications were hitting against memory size limitations.

Resolution:

The default MaxPermSize for all Java applications has been increased to 64MB.

Radar #3710160

Java profiling agent library locations.

Description:

Java profiling agent libraries had to be installed in /System/Library/Frameworks/JavaVM.framework/Libraries/.

Resolution:

Java profiling agent libraries can now be installed in /System/Library/Java/Extensions/ or /Library/Java/Extensions/.

Java Plugin

Radar #3168316

Applet cache is invisible to the user.

Description:

The Java applet cache was stored in ~/.java/deployment/, which is not visible to the user. If the user was low on disk space and had run a number of applets, the only way to free up space was to run the Java 1.4.2 Plugin Settings application.

Resolution:

The Applet cache has been moved to ~/Library/Caches/Java Applets/. This change makes it clearer to identify large directories that can safely be removed.

Radar #3505649

Various Java Plugin improvements.

Description:

There were various issues involving the Java Plugin and AWT events, applet sizing, and standard Java applet properties.

Resolution:

The Java Plugin now uses more standard Java Plugin code from Sun when running applets. Due to these changes, AWT Events are now delivered properly. Dynamically sized applets and standard Java applet properties are also supported.

Note that in fixing these issues, these files have been removed:

Java Security

Radar #3527098

Keystore issues between Java versions.

Description:

A JCE keystore written by the Java 1.4.1 virtual machine (VM) could not be read using the Java 1.4.2 VM.

Resolution:

The Java 1.4.2 VM can now read JCE keystores written by the Java 1.4.1 VM. This is related to Sun bug 4887561, as fixed in the Java 1.4.2_05 VM.



< Previous PageNext Page > Hide TOC


© 2004 Apple Computer, Inc. All Rights Reserved. (Last updated: 2004-08-11)


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.