Home > Articles > Programming > Java

📄 Contents

  1. Design Patterns in General / The Command Pattern and Java 8
  2. Hiding Complexity with the Adaptor Pattern / Installing Java 8
Like this article? We recommend

Hiding Complexity with the Adaptor Pattern

Returning to the device management domain introduced above, suppose I want to model another set of behaviors and attributes. In this case, I want to model accessing and modifying some device attributes. However, my requirement is to decouple this code as far as possible from any low-level device code. Sounds complicated, but again patterns come to the rescue!

Listing 6 illustrates an interface for interacting with a low-level device.

Listing 6: Low-level device access interface

public interface DeviceAccess {
    public String getdeviceName();
    public void setdeviceName(String deviceName);
    public String getdeviceSoftwareVersion();
    public void backupDeviceConfig();

Such a device might be a network router or a switch. Typically, when the interface methods in Listing 6 are implemented, the actual device interaction will use complex device-specific technology such as SNMP and even piped command lines. It's a good design principle to decouple your application code as far as possible from such low-level code. The Adaptor pattern helps to decouple these codebases.

Listing 7 illustrates a fictitious implementation of the interface.

Listing 7: Low-level device access implementation

public class DeviceAccessImpl implements DeviceAccess {

    private String deviceName = null;

    public String getdeviceName() {
        // Make calls into SNMP and/or other domain languages
        if (deviceName == null) {
            return "Super New Device";
        } else {
            return deviceName;

    public void setdeviceName(String deviceName) {
        // Make calls into SNMP etc. to set the device name
        this.deviceName = deviceName;

    public String getdeviceSoftwareVersion() {
        // Make calls into SNMP and/or other domain languages
        return "Super New Device Version 1.0.1";

    public void backupDeviceConfig() {
        System.out.println("Now starting device backup procedure");

Notice the implementation code for the getdeviceName() method:

public String getdeviceName() {
    // Make calls into SNMP and/or other domain languages
    if (deviceName == null) {
        return "Super New Device";
    } else {
        return deviceName;

Typically, this method will do a lot of complicated domain-specific code, calling SNMP libraries or other technologies. Notice also the method name is a little odd: getdeviceName(). Strictly speaking, this should really be getDeviceName(), with a capital D. As this code will generally be provided to you by a device programmer, it's unlikely that you'll be able to apply the above correction. Instead, you can hide the inconsistency using the Adaptor interface as shown in Listing 8.

Listing 8: An Adaptor interface

public interface DeviceManagement {
    public String getDeviceName();
    public void setdeviceName(String deviceName);
    public String getDeviceSoftwareVersion();

The purpose of the interface in Listing 8 is to hide the complexity of Listing 6 and Listing 7. To see how this is done, look at the implementation in Listing 9.

Listing 9: An Adaptor implementation

public class DeviceManagementImpl implements DeviceManagement {

    private DeviceAccess deviceAccess;

    public DeviceManagementImpl() {
        deviceAccess = new DeviceAccessImpl();

    public String getDeviceName() {
        return deviceAccess.getdeviceName();

    public void setdeviceName(String deviceName) {

    public String getDeviceSoftwareVersion() {
        return deviceAccess.getdeviceSoftwareVersion();

     * @param args
    public static void main(String[] args) {
        DeviceManagementImpl deviceManagement = new DeviceManagementImpl();
        System.out.println("Device name: " + deviceManagement.getDeviceName());
        deviceManagement.setdeviceName("Souped up device");
        System.out.println("Device name: " + deviceManagement.getDeviceName());

The important part of Listing 9 is the private member that stores an instance of the device:

private  DeviceAccess deviceAccess;

The methods in DeviceManagementImpl hide the complexity of the DeviceAccess interface. Listing 10 illustrates a simple program run showing the device details before and after a name-change operation:

Listing 10: An Adaptor implementation run

Device name: Super New Device
Device name: Souped up device

We use the Adaptor pattern to hide the complexity of the device access code. Using the Java 8 features, we can also extend the Adaptor interface in exactly the same way as we did for the Command pattern.

Installing Java 8

Getting up and running with Java 8 is easy. If you're running Ubuntu, just run the following commands:

sudo apt-get purge openjdk*

sudo apt-get install python-software-properties
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java8-installer
java -version

The java -version command should produce output similar to the following:

java version "1.8.0"
Java(TM) SE Runtime Environment (build 1.8.0-b132)
Java HotSpot(TM) 64-Bit Server VM (build 25.0-b70, mixed mode)

If you see this output, you're good to go with Java 8.


Patterns remain an extremely useful addition to the programmer toolkit. The generic nature of design patterns makes them pretty easy to include in most programming domains—telecommunications, financial services, energy management systems, and so on.

The Command pattern provides a simple model for implementing instruction-style object interactions such as switch on/off, do/undo, and so forth. By storing the current state, the command implementation allows for any state changes to be reversed. Obviously, this state storage introduces potential concurrency issues, but this is a small price to pay for the rich design semantics that come with the Command pattern. In any case, there are good concurrency patterns that help reduce issues of state contention and deadlocks.

The Java 8 facilities and the Command pattern make a good team, because Java 8 provides the ability to add default methods to interfaces. This in turn obviates the need to change the clients or implementers of those interfaces.

The Adaptor pattern allows for easy modeling of one of the pillars of programming: encapsulation. Third-party code can be easily decoupled from application code by putting the former inside an Adaptor class. This serves two purposes: Separation of Concerns and easier upgrades. The third-party code can then be changed without necessarily breaking the application code. The application code also can be upgraded more easily when it's not directly dependent on the third-party code.

Just as is the case for the Command pattern, the Adaptor pattern can be accommodated inside Java 8 features.

Will I continue to encourage the use of design patterns? You can count on it!

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