Outstanding Issues

This chapter provides a listing of bugs that you may need to work around in your Java code for Mac OS X. Where possible, workarounds are provided.

Java AWT

Radar #4031021

Window.setAlwaysOnTop is ignored by FileDialog and PrintDialog

Description:

Window.setAlwaysOnTop allows for windows to appear above all other windows. However, because FileDialog and PrintDialog use system-defined windows, they do not respect this property.

Workaround:

Use the Swing equivalents of FileDialog and PrintDialog .

Radar #4205435

Nested Dialogs

Description:

Nested modal dialogs don't behave properly if they all use a common parent.

Workaround:

Use the previous modal dialog as the current dialog’s parent.

Java Developer

Radar #4090917

Xcode Java Projects in J2SE 5.0

Description:

The Java projects in Xcode are set up for use with J2SE 1.4.2.

Workaround:

Follow these steps to modify projects for use with J2SE 5.0:

Target Settings:

Double click the target to edit and provide /System/Library/Frameworks/JavaVM.framework/Versions/1.5/Commands/javac as the value for the JAVA_COMPILER build setting. Change the Target VM Version and Source Version in the Java Compiler Setting to use 1.5.

Executable Settings:

Double click the executable named java and enter /System/Library/Frameworks/JavaVM.framework/Versions/1.5/Commands/java as the Executable Path in the General tab of Executable info.

Applet Development:

Double click the executable named appletviewer and enter /System/Library/Frameworks/JavaVM.framework/Versions/1.5/Commands/appletviewer as the Executable Path in the General tab of Executable info.

Radar #4090919

J2SE 5.0 Reference Documentation

Description:

The J2SE 5.0 Reference Documentation is not installed automatically.

Workaround:

Install the latest J2SE 5.0 Developer package, available from http://connect.apple.com.

Radar #4124800

J2SE 5.0 symbols not visible in Xode Documention window.

Description:

After installing the J2SE 5.0 Reference documentation or a documentation update in Xcode, J2SE 5.0 symbols are not present in the Xcode documentation window.

Workaround:

You need to manually run the pbhelpindexer utility in order for J2SE 5.0 symbols to appear in the Xcode Documentation window. First, open MacOSXDeveloper.pbHelpIndexerList, located at:

/Developer/ADC Reference Library/indexes/

Replace this path:

/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Resources/

With this path:

/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Resources/

Finally, run this command in Terminal:

sudo /Developer/Tools/pbhelpindexer

Java Graphics

Radar #3726347

Java2D OpenGL Pipeline Not Supported

Description:

The sun.java2d.opengl package is not supported in J2SE 5.0 Release 1.

Workaround:

None.

Java Security

Radar #4078337

Certificates for SSL client authentication and Keychain

Description:

J2SE 5.0 Release 1 looks in Keychain for certificates when attempting to establish trust for signed applets and https sessions. It currently does not look in the Keychain for sites that also need client authentication.

Workaround:

Create a keystore at ~/Library/Caches/Java/security/trusted.clientcerts and import certificates for client authentication.

Java Virtual Machine

Radar #3499564

jvmstat Tools Not Supported

Description:

Executing the jinfo, jmap, and jstack commands found in /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands results in java.lang.NoClassDefFoundError.

Workaround:

None.

Radar #4084603

JMX Remote Access Configuration File Missing

Description:

Executing J2SE 5.0 applications using the -Dcom.sun.management.jmxremote argument set results in this error:

Error: Config file not found: /System/Library/Frameworks/JavaVM.framework/ Versions/1.5.0/Home/lib/management/management.properties

Workaround:

None.

Java Web Start

Radar #4074412

'association' Element of 'information' Descriptor Ignored

Description:

Java Cache Viewer does not support JNLP applications that have an 'association' element in their 'information' descriptor. The application works as desired, but any declared associations are not registered with LaunchServices when a desktop application is created.

Workaround:

None.

Radar #4075884

JNLP Application Memory Settings

Description:

If a JNLP application specifies a custom memory setting, that setting is not copied into the Java dictionary of the Info.plist when a user creates a desktop application.

Workaround:

Use Property List Editor to add the memory settings to the VMOptions entry of the Java dictionary.

Radar #4088809

Resaving Desktop Web Start Applications

Description:

Launching a double-clickable JNLP application after it's been modified causes the Save dialog to appear again.

Workaround:

Save the double-clickable Web Start application again. Cancelling causes the original double-clickable Web Start application to be deleted.