Open Credo

July 13, 2015 | Software Consultancy

New Tricks with Dynamic Proxies in Java 8 (part 1)

Why Use Dynamic Proxies?

Dynamic proxies have been a feature of Java since version 1.3. They were widely used in J2EE for remoting. Given an abstract interface, and a concrete implementation of that interface, a call to some method on the interface can be made “remote” (i.e. cross-JVM) by creating two additional classes. The first, a “marshalling” implementation of the interface, captures the details of the call in the source JVM and serializes them over the network. The second, an “unmarshalling” endpoint, receives the serialized call details and dispatches the call to an instance of the concrete class on the target JVM.

WRITTEN BY

Dominic Fox

Dominic Fox

New Tricks with Dynamic Proxies in Java 8 (part 1)

Without dynamic proxies and reflection, the developer would have had to provide these two classes for every interface that was to be used remotely. A dynamic proxy is a run-time generated class, implementing one or more interfaces, that automatically converts every method call to one of those interfaces into a call to the invoke method on a provided implementation of java.runtime.InvocationHandler:

Diagram showing proxy and invocation handler

The InvocationHandler can then make decisions about how to handle the call, making use of all the information available at runtime about the method, including annotations, parameter types and the method’s return type. This makes it possible to implement generic logic defining how calls should be dispatched. Once you have written a marshalling InvocationHandler, you can use proxies calling this handler to perform marshalling for all interfaces, instead of having to write a separate implementation for each interface.

Remoting has fallen somewhat out of favour in recent years, as developers have come to understand that method call dispatch and sending a request over the network have fundamentally different semantics and failure modes, but dynamic proxies are still in the language. In this post, I’m going to discuss one of their possible uses for other purposes; in subsequent posts, I’ll talk about some new implementation techniques for dynamic proxies that are opened up by Java 8’s lambdas and default interface methods.

Magic Matchers

For some years now I’ve been using “magic” objects to make it easier to write concise, fluent tests. I define a “magic” object as an object defined purely through an interface, and instantiated via a dynamic proxy which interprets the interface in order to generate the desired behaviour. Of particular use in testing are “magic builders” for generating test values, and “magic matchers” for expressing assertions about the properties of test results. I’m going to concentrate on matchers here.

Suppose we have a class, Person, which is a typical bean-like object with private fields exposed via getter and setter methods.

Using plain old Hamcrest, we have two ways of expressing assertions about instances of this class. One is to extract the values of its properties independently, and test them with separate assertions:

The other is to use the allOf and hasProperty matchers to express a compound expectation about the object as a whole:

This works well enough, but the way Hamcrest describes the compound matcher and reports mismatches is far from helpful:

The hasProperty matcher also weakens the type-consistency of the code: we can write hasProperty("age", containsString("Smith")) and the type-checker won’t object.

What we really want is a fluent API that enables us to say something like this:

and which reports mismatches in a nice, readable format like this:

It’s easy enough to write a custom Hamcrest matcher that has this behaviour, but tedious to have to do it lots of times. Fortunately, we can use dynamic proxies to help us out. We begin by defining a fluent interface containing the methods we want to define our compound matcher:

We then use a static method on a class called MagicMatcher to obtain a dynamic proxy which implements this interface, capturing the conditions expressed through the method calls:

Each method call is “interpreted” by the proxy, which derives a property name (“age”) from the method name (“withAge”) and figures out which method on the matched object to call to get the property value (“getAge”). The property names and corresponding matchers are stored until match or describeMismatch are called on the proxy (which is why the interface must extend Matcher), at which point they are used to extract and test the object’s properties and if necessary build a mismatch report.

This approach is lightweight enough that we can introduce new custom matcher interfaces wherever we need them, re-use them across tests, and get all the benefits of writing custom Hamcrest matchers without actually having to write their implementations. All of the information needed to generate the matcher’s behaviour is present in its interface: we only need to implement, just once, the logic to interpret it and create a suitable InvocationHandler.

In next post I’m going to build up a small library of useful, composable functions for working with dynamic proxies in Java 8, and demonstrate some ways in which these functions can be used to implement a variety of proxying behaviours, including interception and the creation of “magic” objects. The source code for this library, including an implementation of the MagicMatcher class discussed in this post, can be found on github.

 

Related links

New Tricks with Dynamic Proxies in Java 8 (Part 2)

RETURN TO BLOG

SHARE

Twitter LinkedIn Facebook Email

SIMILAR POSTS

Blog