IBM 64-bit SDK for Windows AMD64/EM64T architecture, Java 2 Technology Edition, Version 1.4.2

User Guide


Copyright information

Note: Before using this information and the product it supports, be sure to read the general information under Notices.

This edition of the User Guide applies to the IBM 64-bit SDK for Windows AMD64/EM64T architecture, Java 2 Technology Edition, Version 1.4.2, and to all subsequent releases, modifications, and service refreshes, until otherwise indicated in new editions.

(C) Copyright Sun Microsystems, Inc. 1997, 2003, 901 San Antonio Rd., Palo Alto, CA 94303 USA. All rights reserved.

(C) Copyright International Business Machines Corporation, 1999, 2007. All rights reserved.

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Preface

Read this User Guide if you want to use the SDK to write Sun Microsystems Java(TM) applications and applets or if you want to use the Runtime Environment to run them. The User Guide provides general information about the SDK and specific information about any differences in the IBM(R) implementation of the SDK. Read this User Guide in conjunction with the more extensive documentation on the Sun Web site: http://java.sun.com.

The SDK is supported on Microsoft(R) Windows(R) XP 64-Bit Edition, Windows Server 2003 64-bit edition, and Windows Vista. The Windows Vista Aero interface is not supported.

The IBM JVM Diagnostics Guide provides more detailed information about the IBM JVM.

Note that the SDK includes the Runtime Environment for Windows, which enables you only to run Java applications. If you have installed the SDK, the Runtime Environment is included.

The terms "Runtime Environment" and "Java Virtual Machine" are used interchangeably throughout this User Guide.

Contents

Copyright information
Preface
Compatibility
Contents of the SDK
Runtime Environment
SDK tools
Tools not included in the IBM SDK
Upgrading the SDK
Using the SDK
Obtaining the IBM build and version number
Setting the path to a tool
Changing the PATH statement
Setting the CLASSPATH
Specifying Java options and system properties
Debugging Java applications
Java Debugger (JDB)
Writing JNI applications
Working with applets
Running applets with the Applet Viewer
Debugging applets with the Applet Viewer
CORBA support
Support for GIOP 1.2
Support for Portable Interceptors
Support for Interoperable Naming Service
System properties for tracing the ORB
System properties for tuning the ORB
Java 2 security permissions for the ORB
ORB implementation classes
RMI over IIOP
Implementing the Connection Handler Pool for RMI
Support for new locales
Enhanced BigDecimal
Enhanced BiDirectional support
Euro symbol support
Transforming XML documents
Using an older version of Xerces or Xalan
Shipping Java applications
Service and support for independent software vendors
Accessibility
iKeyman accessibility
Large Swing menu accessibility
Keyboard traversal of JComboBox components in Swing
JConsole
General note about security
Known limitations
Any comments on this User Guide?
Notices
Trademarks

Compatibility

The SDK is a development environment for writing applets and applications that conform to the Sun Microsystems Java 1.4 Core Application Program Interface (API).

In general, any applet or application that ran with version 1.3.1, 1.4.0, or 1.4.1 of the IBM SDK for Windows, Java 2 Technology Edition, or with IBM Cross Platform Technologies for Windows v 2.0, should run correctly with IBM 64-bit SDK for Windows, v1.4.2. Applets that depend on Java 1.4 APIs do not run on browsers that do not support these APIs .

The IBM 64-bit SDK for Windows, v1.4.2 does not include a Plug-in.

There is no guarantee that 1.4 compiled classes would work on pre-1.4.0 releases.

To read Sun's documentation on compatibility, search for it on the Sun Web site at http://java.sun.com.

The IBM 64-bit SDK for Windows, v1.4.2 does not support the NTLM authentication scheme.

Contents of the SDK

The SDK contains several development tools and a Java Runtime Environment (JRE). This section describes the contents of the SDK tools and the Runtime Environment.

Applications written entirely in Java should have no dependencies on the IBM SDK's directory structure (or files in those directories). Any dependency on the SDK's directory structure (or the files in those directories) could result in application portability problems.

Runtime Environment

Earlier versions of the IBM JRE shipped with a file called rt.jar in the jre/lib directory. From Java v1.4 onwards, this file has been replaced by multiple JAR files that reside in the jre/lib directory. Examples of these JAR files are:

This change should be completely transparent to the application. If an error is received about a missing rt.jar file in CLASSPATH, this error points to a setting that was used in Java v1.1.8 and was made obsolete in subsequent versions of Java. You can safely remove references to rt.jar in CLASSPATH.

SDK tools

Note: The User Guides and the accompanying license, copyright files, and demo directory are the only documentation that is included in this SDK for Windows. You can view Sun's software documentation by visiting the Sun Web site, or you can download Sun's software documentation package from the Sun Web site: http://java.sun.com.

Tools not included in the IBM SDK

The following tools are not included in the IBM SDK:

Upgrading the SDK

If you are upgrading the SDK from a previous release, back up all the configuration files and security policy files before you go ahead with the upgrade.

After the upgrade, you might have to restore or reconfigure these files because they might have been overwritten during the upgrade process. Check the syntax of the new files before restoring the original files because the format or options for the files might have changed.

Using the SDK

The following sections provide information about using the SDK.

Obtaining the IBM build and version number

To obtain the IBM build and version number, at a command prompt type:

java -version

Setting the path to a tool

The Java tools are Windows programs that are run from a command prompt. After installing the SDK software, you run a tool by typing its name at a command prompt with a filename as an argument.

You can specify the path to a tool by typing the path in front of the tool each time. For example, if the javac compiler is in C:\Program Files\IBM\Java142\bin, you can compile a file named myfile.java by typing the following at a command prompt:

C:\Program Files\IBM\Java142\bin\javac myfile.java

Alternatively, you can add the string C:\Program Files\IBM\Java142\bin to your PATH statement. Then, you can compile the myfile.java file by typing the following at a command prompt:

javac myfile.java

The PATH statement enables Windows to find the executable files (such as javac.exe, java.exe, javadoc.exe) from any directory. To find the current value of your PATH, type the following at a command prompt:

path

Changing the PATH statement

To change the PATH statement:

  1. Select on Control Panel.
  2. Select on Performance and Maintenance.
  3. Select on System.
  4. Select Environment Variables on the Advanced tab. A list of system variables is displayed.
  5. Select Path and modify the variable by adding the new directory in the Value text box.
  6. To make the path take effect, select OK.

Previously opened command prompt windows do not reflect the changes. Close and reopen the command prompt windows to see the changes.

Setting the CLASSPATH

The CLASSPATH tells the Java Virtual Machine (JVM) and other JVM applications where to find classes that you develop. If you do not set the CLASSPATH, the default is the current directory (".").

You can set the classpath at runtime by using the option -classpath. For example:

java -classpath <directory> <class>

Where <directory> is the directory where the classes you want to use are located, and <class> is the Java class you want to run. See the IBM 64-bit Runtime Environment for Windows AMD64/EM64T architecture, Java 2 Technology Edition, Version 1.4.2 User Guide for more details.

To set the CLASSPATH to include a particular class of an application, follow this model:

    set classpath=C:\java\apps\classes;%classpath%

where [C:\java\apps\classes] is the drive and path to the application and its classes.

To reset the CLASSPATH to null and remove unwanted classes, type the following at a command prompt:

    set classpath=

Use the Control Panel to make a permanent change to the CLASSPATH in the same way that you change the PATH. See the section Changing the PATH statement.

Specifying Java options and system properties

You can specify Java options and system properties by creating an environment variable called IBM_JAVA_OPTIONS and setting it to the values you require. Any Java options or system properties specified must be preceded by a space, except for the first option. For example, you could set IBM_JAVA_OPTIONS as follows:

IBM_JAVA_OPTIONS=-Dmysysprop1=tcpip -Dmysysprop2=wait

If you specify the same options or properties from the command line (or from a JNI program), these take precedence over the options and properties specified by the IBM_JAVA_OPTIONS environment variable. The only exception to this rule is when specifying -Xt, -Xtm, or -Xdebug, all of which imply that no JIT should be used.

Note:
Java options should be specified in their current format, for example, -verbose:gc rather than -verbosegc.

Debugging Java applications

To debug Java programs, you can use the Java Debugger (JDB) application or other debuggers that communicate by using the Java Platform Debugger Architecture (JPDA) that is provided by the SDK for Windows.

Java Debugger (JDB)

The Java Debugger (JDB) is included in the SDK for Windows. The debugger is invoked by the jdb command; it "attaches" to the JVM using JPDA. To debug a Java application:

  1. Start the JVM with the following options:
    java -Xdebug -Xrunjdwp:transport=dt_socket,server=y,
    address=<port number> 
     MyApplication <MyApplication args>
  2. The JVM starts up, but suspends execution before it starts the Java application. In a separate session, you can attach the debugger to the JVM:
    jdb -attach <port number>
    The debugger will attach to the JVM, and you can now issue a range of commands to examine and control the Java application, for example type "run" to allow the Java application to execute.

To find out more about JDB options, type:

jdb -help

To find out more about JDB commands:

  1. Type jdb
  2. At the jdb prompt, type help

You can also use JDB to debug remote Java applications:

  1. Start the JVM as before.
  2. Attach the debugger to the remote machine:
    jdb -attach <machine name or ip address>:<port number>

When you launch a debug session using the dt_socket transport, be sure that the specified ports are free to use.

The Java Virtual Machine Debugging Interface (JVMDI) is not supported.

For more information on JDB and JPDA and their usage see the following Web sites:


Writing JNI applications

Valid JNI version numbers that native programs can specify on the JNI_CreateJavaVM() API call are:

This version number determines only the level of the JNI native interface to use. The actual level of the JVM that is created is specified by the J2SE libraries (that is, v1.4.2). The JNI interface API does not affect the language specification that is implemented by the JVM, the class library APIs, or any other area of JVM behavior. For further information see http://java.sun.com/j2se/1.4.2/docs/guide/jni.

Use the com.ibm.vm.bitmode system property to determine if you're running with a 32- or 64-bit JVM. An application that has two JNI libraries, one built for 32-bit and the other for 64-bit, can use this system property to operate with both 32- and 64-bit JVMs. At runtime the Java code can select which library to load based on the value of com.ibm.vm.bitmode.

Note:
Version 1.1 of the Java Native Interface (JNI) is not supported.

Working with applets

Running applets with the Applet Viewer

With the Applet Viewer, you can run one or more applets that are called by reference in a Web page (HTML file) by using the APPLET tag. The Applet Viewer finds the APPLET tags in the HTML file and runs the applets, in separate windows, as specified by the tags.

Because the Applet Viewer is for viewing applets, it cannot display a whole Web page that contains many HTML tags. It parses only the APPLET tags and no other HTML on the Web page.

To run an applet with the Applet Viewer, type the following at a command prompt:

   appletviewer name

where name is one of the following:

For example, to invoke the Applet Viewer on an HTML file that calls an applet, type at a command prompt:

bin\appletviewer demo\GraphLayout\example1.html

where bin is replaced by the full path to the Developer Kit's bin directory.

For example, http://java.sun.com/applets/NervousText/example1.html is the URL of a Web page that calls an applet. To invoke the Applet Viewer on this Web page, type at a shell prompt:

bin\appletviewer http://java.sun.com/applets/NervousText/example1.html


where bin is replaced by the absolute path to the Developer Kit's bin directory.

The Applet Viewer does not recognize the charset option of the <META> tag. If the file that appletviewer loads is not encoded as the system default, an I/O exception might occur. To avoid the exception, use the -encoding option when you run appletviewer. For example:

appletviewer -encoding JISAutoDetect sample.html

Debugging applets with the Applet Viewer

You can debug applets by using the -debug option of the Applet Viewer. When debugging applets, you are advised to invoke the Applet Viewer from the directory that contains the HTML file that calls the applet. For example:

cd demo\TicTacToe
bin\appletviewer -debug example1.html

You can find documentation about how to debug applets using the Applet Viewer at the Sun Web site: http://java.sun.com.


CORBA support

The Java 2 Platform, Standard Edition (J2SE) supports, at a minimum, the specifications that are defined in the Official Specifications for CORBA support in J2SE V1.4 at http://java.sun.com/j2se/1.4.2/docs/api/org/omg/CORBA/doc-files/compliance.html. In some cases, the IBM J2SE ORB supports more recent versions of the specifications.

Support for GIOP 1.2

This SDK supports all versions of GIOP, as defined by chapters 13 and 15 of the CORBA 2.3.1 specification, OMG document formal/99-10-07, which you can obtain from:

http://www.omg.org/cgi-bin/doc?formal/99-10-07

Bidirectional GIOP is not supported.

Support for Portable Interceptors

This SDK supports Portable Interceptors, as defined by the OMG in the document ptc/01-03-04, which you can obtain from:

http://www.omg.org/cgi-bin/doc?ptc/01-09-58

Portable Interceptors are hooks into the ORB through which ORB services can intercept the normal flow of execution of the ORB.

Support for Interoperable Naming Service

This SDK supports the Interoperable Naming Service, as defined by the OMG in the document ptc/00-08-07, which you can obtain from:

http://www.omg.org/cgi-bin/doc?ptc/00-08-07

The default port that is used by the Transient Name Server (the tnameserv command), when no ORBInitialPort parameter is given, has changed from 900 to 2809, which is the port number that is registered with the IANA (Internet Assigned Number Authority) for a CORBA Naming Service. Programs that depend on this default might have to be updated to work with this version.

The initial context that is returned from the Transient Name Server is now an org.omg.CosNaming.NamingContextExt. Existing programs that narrow the reference to a context org.omg.CosNaming.NamingContext still work, and do not need to be recompiled.

The ORB supports the -ORBInitRef and -ORBDefaultInitRef parameters that are defined by the Interoperable Naming Service specification, and the ORB::string_to_object operation now supports the ObjectURL string formats (corbaloc: and corbaname:) that are defined by the Interoperable Naming Service specification.

The OMG specifies a method ORB::register_initial_reference to register a service with the Interoperable Naming Service. However, this method is not available in the Sun Java Core API at Version 1.4.2. Programs that need to register a service in the current version must invoke this method on the IBM internal ORB implementation class. For example, to register a service "MyService":

((com.ibm.CORBA.iiop.ORB)orb).register_initial_reference("MyService",
serviceRef); 

where orb is an instance of org.omg.CORBA.ORB, which is returned from ORB.init(), and serviceRef is a CORBA Object, which is connected to the ORB.This mechanism is an interim one, and is not compatible with future versions or portable to non-IBM ORBs.

System properties for tracing the ORB

A runtime debug feature provides improved serviceability. You might find it useful for problem diagnosis or it might be requested by IBM service personnel. Tracing is controlled by three system properties.

For example, to trace events and formatted GIOP messages, type:

 java -Dcom.ibm.CORBA.Debug=true  
		-Dcom.ibm.CORBA.CommTrace=true myapp   

Do not turn on tracing for normal operation, because it might cause performance degradation. Even if you have switched off tracing, FFDC (First Failure Data Capture) is still working, so that only serious errors are reported. If a debug output file is generated, examine it to check on the problem. For example, the server might have stopped without performing an ORB.shutdown().

The content and format of the trace output might vary from version to version.

System properties for tuning the ORB

The following properties help you to tune the ORB:

Java 2 security permissions for the ORB

When running with a Java 2 SecurityManager, invocation of some methods in the CORBA API classes might cause permission checks to be made, which might result in a SecurityException. Affected methods include the following:

Table 1. Methods affected when running with Java 2 SecurityManager
Class/Interface Method Required permission
org.omg.CORBA.ORB

init

java.net.SocketPermission resolve

org.omg.CORBA.ORB

connect

java.net.SocketPermission listen

org.omg.CORBA.ORB

resolve_initial_references

java.net.SocketPermission connect

org.omg.CORBA.
portable.ObjectImpl

_is_a

java.net.SocketPermission connect

org.omg.CORBA.
portable.ObjectImpl

_non_existent

java.net.SocketPermission connect

org.omg.CORBA.
portable.ObjectImpl

OutputStream _request (String, boolean)

java.net.SocketPermission connect

org.omg.CORBA.
portable.ObjectImpl

_get_interface_def

java.net.SocketPermission connect

org.omg.CORBA.
Request

invoke

java.net.SocketPermission connect

org.omg.CORBA.
Request

send_deferred

java.net.SocketPermission connect

org.omg.CORBA.
Request

send_oneway

java.net.SocketPermission connect

javax.rmi.
PortableRemoteObject

narrow

java.net.SocketPermission connect

If your program uses any of these methods, ensure that it is granted the necessary permissions.

ORB implementation classes

The ORB implementation classes in this release are:

These are the default values, and you are advised not to set these properties or refer to the implementation classes directly. For portability, make references only to the CORBA API classes, and not to the implementation. These values might be changed in future releases.

RMI over IIOP

Java Remote Method Invocation (RMI) provides a simple mechanism to do distributed Java programming. RMI over IIOP (RMI-IIOP) uses the Common Object Request Broker Architecture (CORBA) standard Internet Inter-ORB Protocol (IIOP protocol) to extend the base Java RMI to perform communication. This allows direct interaction with any other CORBA Object Request Brokers (ORBs), whether they were implemented in Java or another programming language.

The following documentation is available:

Implementing the Connection Handler Pool for RMI

Thread pooling for RMI Connection Handlers is not enabled by default.

To enable the connection pooling implemented at the RMI TCPTransport level, set the option

-Dsun.rmi.transport.tcp.connectionPool=true (or any non-null value) 

This version of the Runtime Environment does not have any setting that you can use to limit the number of threads in the connection pool.

For more information, see the Sun Java site: http://java.sun.com.

Support for new locales

From Service Refresh 8, the following new locale is added: Serbia (SE), with these three new locale variations:

The existing locale variations for the former Serbia and Montenegro are maintained as before. The 3-letter country code SRB, corresponding to the 2-letter country code RC, is also added.

Enhanced BigDecimal

The SDK includes an enhanced BigDecimal class (com.ibm.math.BigDecimal) for Java programming. It is provided (with its supporting class MathContext) as an alternative to the java.math.BigDecimal class.

The java.math.BigDecimal class provides a minimal, fixed-point, decimal arithmetic capability only. The com.ibm.math.BigDecimal class adds:

The com.ibm.math.BigDecimal class uses significantly fewer resources for common operations than the java.math.BigDecimal class.

The com.ibm.math.BigDecimal class is compatible with java.math.BigDecimal, and supports all of its methods. To use the com.ibm.math.BigDecimal class, change the import statement at the top of your .java file: import java.math,*; to import com.ibm.math.*;.

For more information see http://www.alphaworks.ibm.com/tech/bigdecimal.

Enhanced BiDirectional support

The IBM SDK includes enhanced BiDirectional support. For more information, see http://www-106.ibm.com/developerworks/java/jdk/bidirectional/index.html.

Euro symbol support

The IBM SDK sets the Euro as the default currency for those countries in the European Monetary Union (EMU) for dates on or after 1 January, 2002.

To use the old national currency, specify -Duser.variant=PREEURO on the Java command line.

If you are running the UK, Danish, or Swedish locales and want to use the Euro, specify -Duser.variant=EURO on the Java command line.

In V1.4.2 SR6, the default for the Slovenian locale is set to the Euro. If you install SR6 before 1 January 2007, you might want to change the currency to the Tolar.

Transforming XML documents

The IBM SDK contains the XSLT4J 2.6 processor and the XML4J 4.3 parser that conform to the JAXP 1.2 specification. These tools allow you to parse and transform XML documents independently from any given XML processing implementation. By using "Factory Finders" to locate the SAXParserFactory, DocumentBuilderFactory and TransformerFactory implementations, your application can swap between different implementations without having to change any code.

The XSLT4J 2.6 processor allows you to choose between the original XSLT Interpretive processor or the new XSLT Compiling processor. The Interpretive processor is designed for tooling and debugging environments and supports the XSLT extension functions that are not supported by the XSLT Compiling processor. The XSLT Compiling processor is designed for high performance runtime environments; it generates a transformation engine, or translet, from an XSL stylesheet. This approach separates the interpretation of stylesheet instructions from their runtime application to XML data.

The XSLT Interpretive processor is the default processor. To select the XSLT Compiling processor you can:

To implement properties in the jaxp.properties file, copy jaxp.properties.sample to jaxp.properties in C:\Program Files\IBM\Java142\jre\lib. This file also contains full details about the procedure used to determine which implementations to use for the TransformerFactory, SAXParserFactory, and the DocumentBuilderFactory.

To improve the performance when you transform a StreamSource object with the XSLT Compiling processor, specify the com.ibm.xslt4j.b2b2dtm.XSLTCB2BDTMManager class as the provider of the service org.apache.xalan.xsltc.dom.XSLTCDTMManager. To determine the service provider, try each step until you find org.apache.xalan.xsltc.dom.XSLTCDTMManager:

  1. Check the setting of the system property org.apache.xalan.xsltc.dom.XSLTCDTMManager.
  2. Check the value of the property org.apache.xalan.xsltc.dom.XSLTCDTMManager in the file C:\Program Files\IBM\Java142\jre\lib\xalan.properties.
  3. Check the contents of the file META-INF\services\org.apache.xalan.xsltc.dom.XSLTCDTMManager for a class name.
  4. Use the default service provider, org.apache.xalan.xsltc.dom.XSLTCDTMManager.

The XSLT Compiling processor detects the service provider for the org.apache.xalan.xsltc.dom.XSLTCDTMManager service when a javax.xml.transform.TransformerFactory object is created. Any javax.xml.transform.Transformer or javax.xml.transform.sax.TransformerHandler objects that are created by using that TransformerFactory object will use the same service provider. You can only change service providers by modifying one of the settings described above and then creating a new TransformerFactory object.

Using an older version of Xerces or Xalan

If you are using an older version of Tomcat, this limitation might apply.

If you are using an older version of Xerces or Xalan in the endorsed override, you might get a null pointer exception when you launch your application. This exception occurs because these older versions do not handle the jaxp.properties file correctly.

To avoid this situation, use one of the following workarounds:

Shipping Java applications

A Java application, unlike a Java applet, cannot rely on a Web browser for installation and runtime services. When you ship a Java application, your software package probably consists of the following parts:

To run your application, a user needs the Runtime Environment for Windows. The SDK for Windows software contains a Runtime Environment. However, you cannot assume that your users have the SDK for Windows software installed.

Your SDK for Windows software license does not allow you to redistribute any of the SDK's files with your application. You should ensure that a licensed version of the SDK for Windows is installed on the target machine.

Service and support for independent software vendors

If you are entitled to services for the Program code pursuant to the IBM Solutions Developer Program, contact the IBM Solutions Developer Program through your normal method of access or on the Web at: http://www-1.ibm.com/partnerworld/.

If you have purchased a service contract (that is, IBM's Personal Systems Support Line or equivalent service by country), the terms and conditions of that service contract determine what services, if any, you are entitled to receive with respect to the Program.

Accessibility

The User Guides that are supplied with this SDK and the Runtime Environment have been tested by using screen readers. You can use a screen reader such as the Home Page Reader or the JAWS screen reader with these User Guides.

To change the font sizes in the User Guides, use the function that is supplied with your browser, usually found under the View menu option.

For users who require keyboard navigation, a description of useful keystrokes for Swing applications is in "Swing Component Keystroke Assignments" at http://java.sun.com/j2se/1.4/docs/api/javax/swing/doc-files/Key-Index.html

iKeyman accessibility

The iKeyman tool has a GUI only; however, the IBM 64-bit SDK for Windows, v1.4.2 provides the command-line tool IKEYCMD, which has the same functions that iKeyman has. IKEYCMD allows you to manage keys, certificates, and certificate requests. You can call IKEYCMD from native shell scripts and from programs that are to be used when applications need to add custom interfaces to certificate and key management tasks. IKEYCMD can create key database files for all the types that iKeyman currently supports. IKEYCMD can also create certificate requests, import CA signed certificates, and manage self-signed certificates.

To run an IKEYCMD command, enter:

java [-Dikeycmd.properties=<properties file>]com.ibm.gsk.ikeyman.ikeycmd
<object><action>[options]

where:

<object>
is one of the following:
-keydb
Actions that are taken on the key database (either a CMS key database file, a WebDB keyring file, or SSLight class)
-version
Displays version information for IKEYCMD
<action>
The specific action that is to be taken on the object. This action is one of the following:
-cert
Actions that are to be taken on a certificate
-certreq
Actions that are to be taken on a certificate request
-Dikeycmd.properties
Specifies the name of an optional properties file to use for this Java invocation. A default properties file, ikeycmd.properties, is provided as a sample file that can be changed and used by any Java application.
-help
Displays help for the IKEYCMD invocations.
Note:
The object and action keywords are positional and must be in the specified sequence. However, options are not positional and can be in any sequence, provided that they are specified as an option and operand pair.

For more information, see the iKeyman User Guide at: http://www-106.ibm.com/developerworks/java/jdk/security/142/ikmuserguide.pdf.

Large Swing menu accessibility

If you have a Swing JMenu that has more entries than can be displayed on the screen, you can navigate through the menu items by using the down or up arrow keys or the keyboard arrows.

Keyboard traversal of JComboBox components in Swing

If you traverse the drop-down list of a JComboBox component with the cursor keys, the button or editable field of the combo box does not change value until an item is selected. This is the desired behavior for this release and improves accessibility and usability by ensuring that the keyboard traversal behavior is consistent with mouse traversal behavior.

JConsole

To enable JConsole to run on Windows with the Windows look and feel, JConsole needs to be launched with the following command line:

java -Dswing.defaultlaf=com.sun.java.swing.plaf.windows.WindowsLookAndFeel JConsole

This will enable the High Contrast color schemes available in windows to be adopted by JConsole.

General note about security

You can obtain JCE unrestricted jurisdiction files from http://www.ibm.com/developerworks/java/jdk/security/index.html. Documentation about the IBM security packages JCE, JSSE, and JGSS will also be made available at this Web site.

Known limitations

Note these limitations in the IBM 64-bit SDK for Windows, v1.4.2:

Any comments on this User Guide?

If you have any comments about the usefulness, or otherwise, of this User Guide, we would be pleased to hear from you through one of these channels. Please note that these channels are not set up to answer technical queries, but are for comments about the documentation only. Send your comments:

The fine print. By choosing to send a message to IBM, you acknowledge that all information contained in your message, including feedback data, such as questions, comments, suggestions, or the like, shall be deemed to be non-confidential and IBM shall have no obligation of any kind with respect to such information and shall be free to reproduce, use, disclose, and distribute the information to others without limitation. Further, IBM shall be free to use any ideas, concepts, know-how or techniques contained in such information for any purpose whatsoever, including, but not limited to, developing, manufacturing and marketing products incorporating such information.

Notices

This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the information. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this information at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

Trademarks

IBM, developerWorks, iSeries, pSeries, AS/400, and PowerPC are trademarks or registered trademarks of International Business Machines Corporation in the United States, or other countries, or both.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both

Other company, product, or service names may be trademarks or service marks of others.

This product is also based in part on the work of the FreeType Project. For more information about Freetype, see http://www.freetype.org.

This product includes software developed by the Apache Software Foundation http://www.apache.org/.