Dynamic Delegation and Its ApplicationsThe Proxy pattern is an important and widely used design pattern in object-oriented programming. Do you ever use
Proxy in Java since its introduction in JDK 1.3? A dynamic proxy class is a class that
implements a list of interfaces specified at runtime. An implementation for the proxy's
behavior can be provided at runtime through an InvocationHandler.
So Proxy is an important
class in Java's reflection package, and is widely used in many Java applications.
One limitation of Proxy is that it can only accept interfaces. In some
circumstances, you need to apply the Proxy pattern not only to interfaces, but also to
abstract classes, and even concrete classes.
This article introduces Dynamic Delegation, which can create delegation for both interfaces and classes at runtime.
In JDK 1.3, the Proxy class was added to java.lang.reflect. It can create a
concrete class that implements all of the specified interfaces at runtime. The dynamically
generated class redirects all of the method calls defined in the interfaces to an InvocationHandler.
Given two interfaces, Idel1 and Idel2, Proxy will create
a IdelProxy class as the proxy of these two interfaces (I use IdelProxy as the generated proxy
class name for convenience). Figure 1 shows this arrangement.

Figure 1. Class diagram of IdelProxy
Below is the related code snippet.
Class clazz = Proxy.getProxyClass(
Idel1.class.getClassLoader(),
new Class[] { Idel1.class, Idel2.class });
Proxy only works for interfaces. What if we need it to work for both classes
and interfaces? The Dunamis project
on java.net introduces Delegation as
an alternative to Proxy.
Delegation uses a different approach than Proxy.
Given a class named TestBean, the delegation class TestBeanDelegation's
class diagram is shown in Figure 2.

Figure 2. Class diagram of TestBeanDelegation (click for full-size image)
TestBeanDelegation implements the Delegation interface and extends the
TestBean class. It also contains references to TestBean and
DelegationInvocationHandler. All of the method calls on TestBeanDelegation
will be delegated to them.
Take getName() as an example. The chart in Figure 3 illustrates the sequence of the method call.

Figure 3. Sequence chart of TestBeanDelegation.getName() (click for full-size image)
The related pseudocode is:
//The delegation class is a sub-class of the class to be delegated
public class TestBeanDelegation extends TestBean
implements Delegation {
//The object to be delegated
TestBean bean;
//The invocation handler
DelegationInvocationHandler handler;
...
static Method m0 = null;
...
static {
...
try {
m0 = TestBean.class.getMethod("getName",
new Class[] {});
} catch (Exception exception) {
}
...
}
public TestBeanDelegation(Object bean) {
this.bean = (TestBean)bean;
}
public String getName() {
boolean goon = true;
String ret = null;
Throwable t = null;
try {
goon = handler.invokeBefore(bean,
m0, new Object[] {});
if (goon)
try {
ret = bean.getName();
} catch (Throwable throwable) {
t = throwable;
}
if (t != null)
ret = handler.invokeAfterException(bean,
m0, new Object[] {}, t);
else
ret = handler.invokeAfter(bean,
m0, new Object[] { name }, null);
return ret;
} catch (RuntimeException e) {
throw e;
} catch (Error e) {
throw e;
} catch (Throwable throwable) {
throw new UndeclaredThrowableException(throwable);
}
}
}
Dynamic Delegation is based on the Jakarta Byte-Code Engineering Library (BCEL). It can analyze the existing class and generate a delegation class in byte code for an interface, abstract class, or even a concrete class at runtime.
|
Related Reading
|
The interface/class to be delegated should meet the following conditions:
This limitation is based on Java's single inheritance model. One Java class can have at most one superclass. Since the generated delegation class takes the given class as its superclass, it is illegal
to specify more than one class. If no class specified, the default superclass is Object.
The delegation class will call the superclass' default constructor in its own constructor.
The proxy class generated by Proxy is final. It will not be accepted by Dynamic Delegation.
Delegation interface.
Since it is already a delegation class, why would you need to delegate it again?
The generated delegation class has the following characteristics:
Delegation interface.Object instance as a parameter.DelegationGenerator is the main class of Dynamic Delegation. A client can use it to generate a delegation
class/object for a specific class/interface/object. DelegationInvocationHandler is an interface
defining all of the delegation behaviors and is expected to be implemented
by the client's developer. The delegation object can use the _getInvocationHandler()
and _setInvocationHandler() methods defined in Delegation to access the DelegationInvocationHandler
instance in the delegation object.
|
Suppose there is a concrete class named ConcreteClass:
//ConcreteClass.java
package org.jingle.util.dydelegation.sample;
public class ConcreteClass {
public void hello() {
System.out.println("Hello from ConcreteClass");
}
protected void hello2() {
System.out.println("Hello again from ConcreteClass");
}
}
The following code generates a delegation class for ConcreteClass.
//ConcreteClassTest.java
package org.jingle.util.dydelegation.sample;
import org.jingle.util.dydelegation.DelegationGenerator;
public class ConcreteClassTest {
public static void main(String[] args) {
Class clazz = DelegationGenerator
.getDelegationClass(new Class[] { ConcreteClass.class });
System.out.println("Delegation class name = " +
clazz.getName());
System.out.println(
ConcreteClass.class.isAssignableFrom(clazz));
}
}
The output shows:
Delegation class name =
org.jingle.util.dydelegation.sample.ConcreteClass_Delegation_0
true
DelegationGenerator.getDelegationClass() accepts a class array as parameter and
return a Java Class that extends/implements the given class/interfaces. By default,
the generated delegation class is in the same package as the class to be delegated.
The delegation class can be instantiated as below:
//object to be delegated
Object obj = ...;
//some concrete invocation handler instance
DelegationInvocationHandler h = ...;
Constructor c = clazz.getConstructor(new Class[] { Object.class });
Object inst = c.newInstance(new Object[] {obj});
((Delegation) inst)._setInvocationHandler(h);
DelegationGenerator can also generate a concrete delegation class for
an abstract class.
//AbstractClass.java
package org.jingle.util.dydelegation.sample;
public abstract class AbstractClass {
public abstract void wave();
}
//AbstractClassTest.java
package org.jingle.util.dydelegation.sample;
import java.lang.reflect.Modifier;
import org.jingle.util.dydelegation.DelegationGenerator;
public class AbstractClassTest {
public static void main(String[] args) {
Class clazz = DelegationGenerator
.getDelegationClass(new Class[] { AbstractClass.class });
System.out.println("Delegation class name = " +
clazz.getName());
System.out.println(
Modifier.isAbstract(clazz.getModifiers()));
}
}
Output:
Delegation class name =
org.jingle.util.dydelegation.sample.AbstractClass_Delegation_0
false
The generated delegation class is a concrete class instead of an abstract class.
DelegationGenerator.getDelegationClass() can accept a class and multiple interfaces simultaneously
to generate a delegation class to delegate the given class and interfaces. Duplicate interfaces will be eliminated.
//Idel1.java
package org.jingle.util.dydelegation.sample.bean;
public interface Idel1 {
public void idel1();
}
//Idel2.java
package org.jingle.util.dydelegation.sample.bean;
public interface Idel2 {
public void idel2();
}
//ComplexClassTest.java
package org.jingle.util.dydelegation.sample;
import org.jingle.util.dydelegation.DelegationGenerator;
import org.jingle.util.dydelegation.sample.bean.Idel1;
import org.jingle.util.dydelegation.sample.bean.Idel2;
public class ComplexClassTest {
public static void main(String[] args) {
Class clazz = DelegationGenerator.getDelegationClass(new Class[] {
ConcreteClass.class, Idel1.class, Idel2.class });
System.out.println(
Idel1.class.isAssignableFrom(clazz));
System.out.println(
Idel2.class.isAssignableFrom(clazz));
System.out.println(
ConcreteClass.class.isAssignableFrom(clazz));
}
}
Output:
true
true
true
The generated delegation class extends the given class ConcreteClass and implements all of
the given interfaces: Idel1 and Idel2.
DelegationGenerator can generate a delegation object directly, according to a specific object to be delegated.
// ConcreteClassTest2.java
package org.jingle.util.dydelegation.sample;
import java.lang.reflect.Method;
import org.jingle.util.dydelegation.DelegationGenerator;
import org.jingle.util.dydelegation.DelegationInvocationHandler;
import org.jingle.util.dydelegation.DummyInvocationHandler;
public class ConcreteClassTest2 {
public static void main(String[] args) {
ConcreteClass inst = new ConcreteClass();
DelegationInvocationHandler handler =
new SimpleHandler();
ConcreteClass delegation = (ConcreteClass)
DelegationGenerator.newDelegationInstance(inst, handler);
delegation.hello();
delegation.hello2();
System.out.println(delegation.toString());
}
}
class SimpleHandler extends DummyInvocationHandler {
public boolean invokeBefore(Object bean,
Method method, Object[] args)
throws Throwable {
System.out.println("Interrupted by SimpleHandler");
return super.invokeBefore(bean, method, args);
}
}
Output:
Interrupted by SimpleHandler
Hello from ConcreteClass
Hello again from ConcreteClass
Interrupted by SimpleHandler
org.jingle.util.dydelegation.sample.ConcreteClass@ef5502
DummyInvocationHandler is a dummy implementation of DelegationInvocationHandler.
It always returns true in invokeBefore(), returns the input result directly in invokeAfter(),
and throws the input throwable directly in invokeAfterException(). The delegation object with
DummyInvocationHandler has same behavior as the object to be delegated.
DelegationGenerator.newDelegationInstance() accepts an object and an DelegationInvocationHandler
instance as parameters. It returns a delegation object to delegate the given object.
All of the methods called on the delegation object will be delegated to the DelegationInvocationHandler instance,
except:
Object class, other than
hashCode(), equals(), and toString().
|
Did you ever want to delegate an object of an existing Java core class? Delegate it as usual.
//DateTest.java
package org.jingle.util.dydelegation.sample;
import java.lang.reflect.Method;
import java.util.Date;
import org.jingle.util.dydelegation.DelegationGenerator;
import org.jingle.util.dydelegation.DelegationInvocationHandler;
import org.jingle.util.dydelegation.DummyInvocationHandler;
public class DateTest {
public static void main(String[] args) {
Date date = new Date();
DelegationInvocationHandler handler =
new DateClassHandler();
Date delegation = (Date) DelegationGenerator
.newDelegationInstance(date, handler);
System.out.println("Delegation class = " +
delegation.getClass().getName());
System.out.println("True date = " +
date.getTime());
System.out.println("Delegation date = " +
delegation.getTime());
}
}
class DateClassHandler extends DummyInvocationHandler {
public Object invokeAfter(Object bean,
Method method, Object[] args,
Object result) throws Throwable {
if (method.getName().equals("getTime")) {
return new Long(((Long)result).longValue() - 1000);
}
return super.invokeAfter(bean, method, args, result);
}
}
Output:
Delegation class = org.jingle.util.dydelegation.Date_Delegation_0
True date = 1099380377665
Delegation date = 1099380376665
When creating a delegation class for a Java core class, the delegation class will not be in the same
package as the Java core class, because the Java security model does not allow a user-defined ClassLoader
to define a class in a package starting with java.
DateClassHandler catches the getTime() method call in invokeAfter(), and
makes the return value 1000 less than the normal return value.
Can Dynamic Delegation do what Proxy does? Absolutely! Dynamic Delegation
covers the functions of Proxy. Given a proper delegation handler, it can simulate the behavior
of a Java Proxy.
// ProxyTest.java
package org.jingle.util.dydelegation.sample;
import java.lang.reflect.Method;
import org.jingle.util.dydelegation.DelegationGenerator;
import org.jingle.util.dydelegation.DelegationInvocationHandler;
import org.jingle.util.dydelegation.DummyInvocationHandler;
import org.jingle.util.dydelegation.sample.bean.Idel1;
import org.jingle.util.dydelegation.sample.bean.Idel2;
public class ProxyTest {
public static void main(String[] args) {
DelegationInvocationHandler handler = new ProxyHandler();
Object delegation =
DelegationGenerator.newDelegationInstance(null,
new Class[] { Idel1.class, Idel2.class },
null, handler);
((Idel1) delegation).idel1();
((Idel2) delegation).idel2();
}
}
class ProxyHandler extends DummyInvocationHandler {
public boolean invokeBefore(Object bean,
Method method, Object[] args)
throws Throwable {
return false;
}
public Object invokeAfter(Object bean,
Method method, Object[] args,
Object result) throws Throwable {
String name = method.getName();
if (name.equals("idel1"))
System.out.println("Hello from idel1");
else if (name.equals("idel2"))
System.out.println("Hello from idel2");
return super.invokeAfter(bean, method, args, result);
}
}
Output:
Hello from idel1
Hello from idel2
ProxyHandler returns false in invokeBefore(), which means all of the method calls on the
delegation object will not be delegated to the original object. It uses invokeAfter() to define
the delegation behavior as being what Proxy does.
DelegationGenerator.newDelegationInstance() has another version. It contains four arguments:
Object to be delegated.
This can be null. If it is not null, it must be an instance of
all of the given classes and interfaces.
Class to be delegated.
This can contain multiple interfaces and, at most, one class.
If null, a system-generated name will be provided.
DelegationInvocationHandler instance, which is used to define the delegation's behavior.From the output, we can see that the delegation object is an instance of both Idel1
and Idel2. Its behavior is just what is defined in the handler.
Until now, we've delegated all of the functions of the specific object. How about just delegating part of the object's functions?
//MyDate.java
package org.jingle.util.dydelegation.sample.bean;
import java.util.Date;
public class MyDate extends Date implements Idel1, Idel2 {
public void idel1() {
}
public void idel2() {
}
}
// MyDateTest.java
package org.jingle.util.dydelegation.sample;
import java.util.Date;
import org.jingle.util.dydelegation.DelegationGenerator;
import org.jingle.util.dydelegation.DelegationInvocationHandler;
import org.jingle.util.dydelegation.DummyInvocationHandler;
import org.jingle.util.dydelegation.sample.bean.Idel1;
import org.jingle.util.dydelegation.sample.bean.Idel2;
import org.jingle.util.dydelegation.sample.bean.MyDate;
public class MyDateTest {
public static void main(String[] args) {
MyDate inst = new MyDate();
DelegationInvocationHandler handler =
new DummyInvocationHandler();
Object delegation =
DelegationGenerator.newDelegationInstance(inst,
new Class[] { Idel1.class, Idel2.class },
null, handler);
System.out.println(delegation instanceof Idel1);
System.out.println(delegation instanceof Idel2);
System.out.println(delegation instanceof Date);
}
}
Output:
true
true
false
MyDate extends Date and implements the Idel1 and Idel2
interfaces. DelegationGenerator.newDelegationInstance() uses a MyDate instance as
the object instance to be delegated, and limits the delegation scope in Idel1 and
Idel2. In other words, the generated delegation object is an instance of Idel1
and Idel2, but not an instance of Date.
The Dunamis project introduces Dynamic Delegation to extend the function of the Java
Proxy reflection utility. It can generate delegation for both classes
and interfaces at runtime. This article introduces Dynamic Delegation in brief with
simple examples. In the real world, Dynamic Delegation can be used in many areas,
such as mock objects in unit testing, Java GUI MVC framework, and more.
Lu Jian is a senior Java architect/developer with four years of Java development experience.
Return to ONJava.com
Copyright © 2009 O'Reilly Media, Inc.