Home > Articles > Programming > Java

Using the Command and Adaptor Patterns in Java 8

📄 Contents

  1. Design Patterns in General / The Command Pattern and Java 8
  2. Hiding Complexity with the Adaptor Pattern / Installing Java 8
Do you think design patterns are outdated? Or do you feel that software design and coding are pretty much one and the same? Design patterns remain a hugely beneficial programming tool. Watch as Stephen B. Morris explores the use of the Command and Adaptor patterns in the brave new world of Java 8.
Like this article? We recommend

Command and Adaptor are two related design patterns, both of which provide a useful form of indirection that hides unnecessary complexity, while at the same time providing a crisp interface:

  • The Command pattern allows for an instruction-style interface: "Run this operation," "Undo this operation," and so on.
  • The Adaptor pattern facilitates decoupling between code elements that are functionally related. In using the Adaptor pattern, typically you have a class X that's very complex. Rather than writing calls directly to class X, the Adaptor class acts as an intermediary. In other words, when inevitable changes are needed, only the Adaptor class has to be changed.

Both the Command and Adaptor patterns are very useful in helping to protect legacy code and reduce the need to change it. This excellent attribute underlines the importance of a solid knowledge of design patterns.

But what about the use of patterns in the functional programming Java 8 world? Have patterns become a thing of the past now that Java 8 offers such exotic artifacts as lambda expressions?

I think that patterns remain one of the great additions to modern programming. Patterns allow for design clarity and facilitate coding economy; once you've decided to use a pattern, you can usually reduce the amount of boilerplate coding for a given task. Meanwhile, Java 8 lambda expressions substantially reduce coding overhead. Pattern use in Java 8 and some of the core features of Java 8 itself therefore have similar driving motivations.

Design Patterns in General

So, I'm a great fan of design patterns! Patterns provide for very clear code, and they allow software designers to articulate the software layout in advance of coding. But nowadays, when designer and coder are often the same person, is pattern programming still worth the effort? Why can't we dispense with all this pattern stuff and just get down to coding? Well, I still subscribe to the belief that the sooner you start to code, the longer the task will take. Using patterns allows for a beneficial delay in starting to code, giving you the chance to step away from the programming task for a clearer look at the task.

In addition to delaying coding by giving more time to the design task, patterns remain a pillar of modern software development. Consider a simple case of a reporting system where a client runs reports based on a data feed from another system. This is usually a natural candidate for the Publish-Subscribe pattern. In this pattern, the publisher maintains a list of interested or registered subscribers. Then, when new data is generated by the publisher, the subscribers are notified.

In this way, the Publish-Subscribe pattern reduces the need for potentially expensive polling mechanisms in the client code. In other words, the publisher informs the client when new data is available, without the need for the client to make unnecessary calls to the publisher. Used in this way, Publish-Subscribe mechanisms allow for more efficient systems.

It should therefore come as no surprise that languages such as Python and Java have readily available Publish-Subscribe code frameworks (for example, the Java 7 Observable). Without any more effort than choosing to use the Publish-Subscribe pattern, you implicitly provide a really useful nonfunctional requirement of efficient intersystem data transfer. Standing on the shoulders of giants (the pattern creators) allows your code to reach new heights!

In this article, we'll look at the Command and Adaptor patterns and see how they stack up in the brave new Java 8 world.

To get started, let's have a look at a simple Command pattern interface called Command in Listing 1.

Listing 1: A simple Java Command pattern interface

public interface Command {
    public void execute();

Listing 1 is about as simple as it gets: just one method called execute() inside an interface. Listing 2 illustrates an extension of the Command interface.

Listing 2: An extension of the Command pattern interface

public interface SwitchableElement extends Command {
    public void enableElement();
    public void disableElement();

Listing 2 models a network device called a switchable element, which is simply a device with one or more physical interfaces that can be enabled and/or disabled. An example of such a device is an Ethernet interface. To see the state (and other details) for an Ethernet interface under Linux, just type the command ifconfig. This command provides a plethora of information for the system Ethernet interfaces, such as the state, the IP address assigned to the interface, the version of IP running, and so on.

Remember: Pretty much all software basically models something in the real world, whether it's a word processing document, an online game, or a global weather simulation.

So, the interface SwitchableElement models the ability to enable and disable such a switchable interface. This is the essence of the command pattern—you use this pattern to "instruct" some element to do something. Likewise, you can code the Command pattern to reverse the instruction, undoing the action.

Going back to the Ethernet interface, if you want to modify the state of an interface from the command line, you just type this:

ifconfig eth1 up/down

Given the above discussion, Listing 3 illustrates an implementation of the interface. Notice that the implementation class in Listing 3 must retain the required state elementState and the previous state (called previousState) in order to support the required undo semantics.

Listing 3: An implementation of the Command pattern interface

public class ManagedElements implements SwitchableElement {

    boolean elementState;
    boolean previousState;

    public ManagedElements(boolean elementState) {
        this.elementState = elementState;
        System.out.println("ManagedElements initial state: " + elementState);

    public boolean getElementState() {
        return elementState;

    public void setElementState(boolean elementState) {
        this.elementState = elementState;

    public void enableElement() {

    public void disableElement() {

    public void execute() {
        previousState = getElementState();

     * @param args
    public static void main(String[] args) {
        ManagedElements managedElements = new ManagedElements(false);
        System.out.println("ManagedElements post-execute() state: " + managedElements.getElementState());
        System.out.println("ManagedElements post-disable() state: " +

In Listing 3, the call to the execute() method serves to modify the interface state from false to true. Then, to implement the undo action, there's a call to managedElements.disableElement(). Listing 4 illustrates an example of running the implementation code.

Listing 4: An implementation of the Command pattern interface

ManagedElements initial state: false
ManagedElements post-execute() state: true
ManagedElements post-disable() state: false

The sample run in Listing 4 shows the initial state of the interface as false or disabled. The interface state then changes to true once the execute() method has run. The interface state changes back to false following the call to disableElement().

The Command Pattern and Java 8

As we've seen, the Command pattern is still useful! Now, what about its use in Java 8? What if we decided that a new method is needed in the SwitchableElement interface? Java 8 allows for the addition of default methods. This fact ties the implementation code for that new method directly to the interface. Listing 5 illustrates this fact with a new method called by the imaginative name of doSomethingElse(), added to the code from Listing 2.

Listing 5: An extension of the Command pattern interface

public interface SwitchableElement extends Command {
    public void enableElement();
    public void disableElement();
    default public void doSomethingElse() { System.out.println("Hello")       };

In the context of modeling a network device, an additional command pattern method could be something like backing up the configuration data for that device. This type of operation becomes important in large networks with many devices. Just as backing up devices is useful in this context, the ability to restore device configuration could be another candidate for addition to Listing 5.

The design decision to use the Command pattern for modeling our domain has paid dividends: Now we can easily extend the code as our requirements change. Java 8 also allows us to add default methods directly to the interface. This in turn reduces the programming burden in the Java interface implementation code; that is, Java 8 default interface code doesn't need a corresponding implementation. The combination of the Command pattern and Java 8 is a happy union!

Now, what about the Adaptor pattern?

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