How to Integrate with the Desktop Class
Java™ Standard Edition version 6 narrows the gap between performance and integration of native applications and Java applications. Along with the new system tray functionality, splash screen support, and enhanced printing for JTables, Java SE version 6 provides the Desktop API (
java.awt.Desktop ) API, which allows Java applications to interact with default applications associated with specific file types on the host platform.
New functionality is provided by the Desktop class. The API arises from the JDesktop Integration Components (JDIC) project. The goal of the JDIC project is to make "Java technology-based applications first-class citizens" of the desktop, enabling seamless integration. JDIC provides Java applications with access to functionalities and facilities provided by the native desktop. Regarding the new Desktop API, this means that a Java application can perform the following operations:
Launch the host system's default browser with a specific Uniform Resource Identifier (URI)
Launch the host system's default email client
Launch applications to open, edit, or print files associated with those applications
The Desktop API uses the host operating system's file associations to launch applications associated with specific file types. For example, if OpenDocument text (.odt) file extensions are associated with the OpenOffice Writer application, a Java application could launch OpenOffice Writer to open, edit, or even print files with that association. Depending on the host system, different applications may be associated with different actions. For example, if a particular file cannot be printed, check first whether its extension has a printing association on the given operating system.
Use the isDesktopSupported() method to determine whether the Desktop API is available. On the Solaris Operating System and the Linux platform, this API is dependent on Gnome libraries. If those libraries are unavailable, this method will return false. After determining that the Desktop API is supported, that is, the
isDesktopSupported() returns true, the application can retrieve a
Desktop instance using the static method getDesktop().
If an application runs in an environment without a keyboard, mouse, or monitor (a "headless" environment), the
getDesktop() method throws a
Once retrieved, the
Desktop instance allows an application to browse, mail, open, edit, or even print a file or URI, but only if the retrieved
Desktop instance supports these activities. Each of these activities is called an action, and each is represented as a
Desktop.Action enumeration instance:
BROWSE— Represents a browse action performed by the host's default browser.
OPEN— Represents an open action performed by an application associated with opening a specific file type.
EDIT— Represents an edit action performed by an application associated with editing a specific file type
Different applications may be registered for these different actions even on the same file type. For example, the Firefox browser may be launched for the OPEN action, Emacs for the EDIT action, and yet a different application for the PRINT action. Your host desktop's associations are used to determine which application should be invoked. The ability to manipulate desktop file associations is not possible with the current version of the Desktop API in JDK 6, and those associations can be created or changed only with platform-dependent tools at this time.
The following example shows the capabilities mentioned above.
isDesktopSupported() Tests whether this class is supported on the current platform. If it is supported, use
getDesktop() to retrieve an instance.