Home > Articles > Programming > Java

Exploring JDK 7, Part 4: New I/O: The Next Generation

Oracle’s release of JDK 7 is expected to occur this coming Fall. This new release will offer a suite of new features for you to learn. In Part 4 of this four-part series, Jeff Friesen presents the next generation of New I/O.
Like this article? We recommend

Like this article? We recommend

Oracle’s release of JDK 7 is expected to occur this coming fall. This new release will offer a suite of new features for you to learn.

This final article in a four-part series that introduces you to some of these features presents the next generation of New I/O. If this is your first stop, be sure to read Part 1, Part 2, and Part 3 first.

Back in 2000, Sun Microsystems launched JSR 51: New I/O APIs for the Java Platform to develop APIs that provide access to an operating system's low-level input/output operations for improving performance. Introduced as part of J2SE 1.4, and according to Wikipedia's New I/O entry, New I/O (NIO) consists of the following APIs:

  • Buffers for data of primitive types
  • Character set encoders and decoders
  • A pattern-matching facility based on Perl-style regular expressions
  • Channels, a new primitive I/O abstraction
  • A file interface that supports locks and memory mapping of files up to Integer.MAX_VALUE bytes (2GB)
  • A multiplexed, non-blocking I/O facility for writing scalable servers (based upon selectors and keys)

JSR 203: More New I/O APIs for the Java Platform ("NIO.2") picks up from where JSR 51 left off. NIO.2, as it's commonly known, addresses significant problems with the java.awt.File-based filesystem interface, introduces asynchronous I/O, and completes functionality not included with JSR 51. The following major components are included in JSR 203:

  • A new filesystem interface that supports bulk access to file attributes, change notification, escape to filesystem-specific APIs, and a service-provider interface for pluggable filesystem implementations
  • An API for asynchronous (as opposed to polled, non-blocking) I/O operations on both sockets and files
  • The completion of the socket-channel functionality defined in JSR 51, including the addition of support for binding, option configuration, and multicast datagrams

This article introduces you to NIO.2.

New Filesystem Interface

Java's File class suffers from significant problems. For example, the delete() and mkdir() methods return a status code instead of throwing an exception when something goes wrong; there's no way to tell the failure's cause. Additional problems include the following:

  • File doesn't provide a method to detect symbolic links. To learn why symbolic link detection is important, and to discover attempts to fix this problem, check out Patrick’s article, How to deal with filesystem softlinks/symbolic links in Java and Links/Aliases/Shortcuts in Java.
  • File provides access to a limited set of file attributes. It doesn't provide access to file permissions and access control lists.
  • File doesn't provide a way to access all of a file's attributes (such as a file's modification time and its type) at one time, which exacts a performance penalty because the filesystem is queried for each attribute request.
  • File's list() and listFiles() methods, which return arrays of filenames and directory names, don't scale to large directories. When listing a large directory over a network, a list()/listFiles() method call might block the current thread for a long period of time. In severe cases, the virtual machine might run out of memory.
  • File doesn't provide methods to copy and move files. Although File provides a renameTo() method that, in some cases, can be used to move a file, its behavior is platform-dependent, meaning that it behaves inconsistently across platforms. According to renameTo()'s documentation, this method might not be able to move a file from one filesystem to another, it might not be atomic, and it might not succeed if a file with the destination abstract pathname already exists.
  • File doesn't provide a change notification facility, which requires an application to poll for changes, resulting in a performance penalty. For example, a server that needs to determine when a new JAR file has been added to a directory would need to poll that directory so that it could load (or reload) the JAR file. Performance suffers because the server's background thread needs to hit the filesystem for each poll.
  • File doesn't allow developers to introduce their own filesystem implementations. For example, a developer might want to store a filesystem in a zip file, or even create an in-memory filesystem.

NIO.2 introduces a new filesystem interface that overcomes these problems and more. This interface consists of the classes and other types located in the new java.nio.file, java.nio.file.attribute, and java.nio.file.spi packages.

These packages provide several entry points. One of these entry points is the java.nio.file.Paths class, which provides a pair of methods for returning a java.nio.file.Path instance (a file reference that locates a file, which doesn't have to exist, via a system-dependent path):

  • public static Path get(String path) constructs a Path instance by converting the given path string and returns this instance.
  • public static Path get(URI uri) constructs a Path instance by converting the given path Uniform Resource Identifier and returns this instance.

Once you have a Path instance, you can use this instance to perform a variety of path operations (returning parts of the path and joining two paths, for example) and a variety of file operations (such as deleting, moving, and copying files).

The need for brevity prevents me from thoroughly exploring Path. For that reason, I'm only demonstrating the former get() method and Path's delete() method in the context of Listing 1's small utility application.

Listing 1—InformedDelete.java

// InformedDelete.java
import java.io.IOException;
import java.nio.file.DirectoryNotEmptyException;
import java.nio.file.NoSuchFileException;
import java.nio.file.Path;
import java.nio.file.Paths;
public class InformedDelete
   public static void main (String [] args)
      if (args.length != 1)
          System.err.println ("usage: java InformedDelete path");
      // Attempt to construct a Path instance by converting the path argument
      // string. If unsuccessful (you passed an empty string as the
      // command-line argument), the get() method throws an instance of the
      // unchecked java.nio.file.InvalidPathException class.
      Path path = Paths.get (args [0]);
          path.delete (); // Attempt to delete the path.
      catch (NoSuchFileException e)
          System.err.format ("%s: no such file or directory%n", path);
      catch (DirectoryNotEmptyException e)
          System.err.format ("%s: directory not empty%n", path);
      catch (IOException e)
          System.err.format ("%s: %s%n", path, e);

InformedDelete employs Path's delete() method to overcome the problem of File's delete() method not identifying a failure's cause. When Path's delete() method detects a failure, it throws a suitable exception:

  • java.nio.file.NoSuchFileException is thrown if the file doesn't exist.
  • java.nio.file.DirectoryNotEmptyException is thrown if the file is a directory that couldn't be deleted because the directory contains at least one entry.
  • A subclass of java.io.IOException is thrown if some other kind of I/O problem occurs. For example, java.nio.file.AccessDeniedException is thrown if the file is read-only.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020