Adapter design pattern is one of the structural design pattern and its used so that two unrelated interfaces can work together. The object that joins these unrelated interface is called an Adapter.
One of the great real life example of Adapter design pattern is mobile charger. Mobile battery needs 3 volts to charge but the normal socket produces either 120V (US) or 240V (India). So the mobile charger works as an adapter between mobile charging socket and the wall socket. We will try to implement multi-adapter using adapter design pattern in this tutorial. So first of all we will have two classes - Volt
(to measure volts) and Socket
(producing constant volts of 120V).
package com.journaldev.design.adapter;
public class Volt {
private int volts;
public Volt(int v){
this.volts=v;
}
public int getVolts() {
return volts;
}
public void setVolts(int volts) {
this.volts = volts;
}
}
package com.journaldev.design.adapter;
public class Socket {
public Volt getVolt(){
return new Volt(120);
}
}
Now we want to build an adapter that can produce 3 volts, 12 volts and default 120 volts. So first of all we will create an adapter interface with these methods.
package com.journaldev.design.adapter;
public interface SocketAdapter {
public Volt get120Volt();
public Volt get12Volt();
public Volt get3Volt();
}
While implementing Adapter pattern, there are two approaches - class adapter and object adapter - however both these approaches produce same result.
Here is the class adapter approach implementation of our adapter.
package com.journaldev.design.adapter;
//Using inheritance for adapter pattern
public class SocketClassAdapterImpl extends Socket implements SocketAdapter{
@Override
public Volt get120Volt() {
return getVolt();
}
@Override
public Volt get12Volt() {
Volt v= getVolt();
return convertVolt(v,10);
}
@Override
public Volt get3Volt() {
Volt v= getVolt();
return convertVolt(v,40);
}
private Volt convertVolt(Volt v, int i) {
return new Volt(v.getVolts()/i);
}
}
Here is the Object adapter implementation of our adapter.
package com.journaldev.design.adapter;
public class SocketObjectAdapterImpl implements SocketAdapter{
//Using Composition for adapter pattern
private Socket sock = new Socket();
@Override
public Volt get120Volt() {
return sock.getVolt();
}
@Override
public Volt get12Volt() {
Volt v= sock.getVolt();
return convertVolt(v,10);
}
@Override
public Volt get3Volt() {
Volt v= sock.getVolt();
return convertVolt(v,40);
}
private Volt convertVolt(Volt v, int i) {
return new Volt(v.getVolts()/i);
}
}
Notice that both the adapter implementations are almost same and they implement the SocketAdapter
interface. The adapter interface can also be an abstract class. Here is a test program to consume our adapter design pattern implementation.
package com.journaldev.design.test;
import com.journaldev.design.adapter.SocketAdapter;
import com.journaldev.design.adapter.SocketClassAdapterImpl;
import com.journaldev.design.adapter.SocketObjectAdapterImpl;
import com.journaldev.design.adapter.Volt;
public class AdapterPatternTest {
public static void main(String[] args) {
testClassAdapter();
testObjectAdapter();
}
private static void testObjectAdapter() {
SocketAdapter sockAdapter = new SocketObjectAdapterImpl();
Volt v3 = getVolt(sockAdapter,3);
Volt v12 = getVolt(sockAdapter,12);
Volt v120 = getVolt(sockAdapter,120);
System.out.println("v3 volts using Object Adapter="+v3.getVolts());
System.out.println("v12 volts using Object Adapter="+v12.getVolts());
System.out.println("v120 volts using Object Adapter="+v120.getVolts());
}
private static void testClassAdapter() {
SocketAdapter sockAdapter = new SocketClassAdapterImpl();
Volt v3 = getVolt(sockAdapter,3);
Volt v12 = getVolt(sockAdapter,12);
Volt v120 = getVolt(sockAdapter,120);
System.out.println("v3 volts using Class Adapter="+v3.getVolts());
System.out.println("v12 volts using Class Adapter="+v12.getVolts());
System.out.println("v120 volts using Class Adapter="+v120.getVolts());
}
private static Volt getVolt(SocketAdapter sockAdapter, int i) {
switch (i){
case 3: return sockAdapter.get3Volt();
case 12: return sockAdapter.get12Volt();
case 120: return sockAdapter.get120Volt();
default: return sockAdapter.get120Volt();
}
}
}
When we run above test program, we get following output.
v3 volts using Class Adapter=3
v12 volts using Class Adapter=12
v120 volts using Class Adapter=120
v3 volts using Object Adapter=3
v12 volts using Object Adapter=12
v120 volts using Object Adapter=120
Some of the adapter design pattern example I could easily find in JDK classes are;
That’s all for adapter design pattern in java.
Thanks for learning with the DigitalOcean Community. Check out our offerings for compute, storage, networking, and managed databases.
While we believe that this content benefits our community, we have not yet thoroughly reviewed it. If you have any suggestions for improvements, please let us know by clicking the “report an issue“ button at the bottom of the tutorial.
Hi Pankaj . Is it what you said about two unrelated interfaces(Mobile & Socket) public interface Socket { Integer getVolts(); } public interface Mobile { Integer getDesiredVolts(); } public class Socket12v implements Socket { @Override public Integer getVolts() { return 12; } } public class Socket3v implements Socket { @Override public Integer getVolts() { return 3; } } public class SocketObjectAdapter implements Mobile { // Using Composition for adapter pattern private Socket socket; public SocketObjectAdapter(Socket s) { this.socket = s; } @Override public Integer getDesiredVolts() { return socket.getVolts(); } } public class AdapterTest { public static void main(String[] args) { Socket soc3v = new Socket3v(); Mobile redmi = new SocketObjectAdapter(soc3v); System.out.println(redmi.getDesiredVolts()); Socket soc12v = new Socket12v(); Mobile onePlus = new SocketObjectAdapter(soc12v); System.out.println(onePlus.getDesiredVolts()); } }
- Awinas Kannan
I think Object Adapter pattern is not Composite pattern in that the composite interface SocketAdapter has no relation with the base type Socket technically. I’d say it’s just the way how Object Adapter pattern is, or if I have to give a pattern for this then I’d say it’s more like Decorator pattern. By the way thank you for your SW design pattern posts. I’m learning about them for job interviews :)
- Changdae Park
Thanks.Very good explanation
- Narendar Singh
very good!I learned it
- hui
Thanks.Very good explanation
- GuruRaja
Thanks a lot… It is well explained…
- Devesh
It’s helpful, it is simple and detailed. I try to understand every design pattern as a designer and use it in our daily working or programming. Thanks.
- Silent
getVolt(sockAdapter,3); --> which method is actually calling ?
- jitesh
Hi, Personally, I would inject Socket instead of letting the adapter to initialize it, e.g public SocketObjectAdapterImpl(Socket s){ this.s = s; } The reason for this change is that if you want to add setters to the Socket, then you won’t be able to set the state from the client as the reference to the object is within the state of the Adapter. I would limit the adapter’s responsibility to getting state and/or converting, nothing more. Any reason why you favour the current implementation over the DI ?
- Pitos
Hi Pankaj, Your example was really good, it did help me understand the adapter pattern. I referenced your post while creating my demo for the same.
- Yogesh