TypeTools
A simple, zero-dependency library for working with types. Supports Java 1.6+ and Android.
Introduction
One of the sore points with Java involves working with type information. In particular, Java's generics do not provide a way to resolve or reify the type information for a given class. TypeTools looks to solve this by fully resolving generic type information declared on any class, interface, lambda expression or method.
Usage
The TypeResolver class provides some of the following methods:
Type reify(Type type, Class<S> context)
Returns a fully reifiedtypeusing type variable information from thecontext.Type reify(Type genericType)
Returns a fully reifiedgenericTypeusing information from the generic declaration.Class<?>[] resolveRawArguments(Class<T> type, Class<S> subType)
Resolves the raw arguments for atypeusing type variable information from asubType.Class<?> resolveRawArgument(Class<T> type, Class<S> subType)
Resolves the raw argument for atypeusing type variable information from asubType.Type resolveGenericType(Class<?> type, Type subType)
Resolves the generictypeusing type variable information from asubType.Class<?> resolveRawClass(Type genericType, Class<?> subType)
Resolves the raw class for agenericTypeusing type variable information from asubType.
Examples
A typical use case is to resolve arguments for a type, given a sub-type:
interface Foo<T1, T2> {}
class Bar implements Foo<Integer, String> {}
Class<?>[] typeArgs = TypeResolver.resolveRawArguments(Foo.class, Bar.class);
assert typeArgs[0] == Integer.class;
assert typeArgs[1] == String.class;
Type arguments can also be resolved from lambda expressions:
Function<String, Integer> strToInt = s -> Integer.valueOf(s);
Class<?>[] typeArgs = TypeResolver.resolveRawArguments(Function.class, strToInt.getClass());
assert typeArgs[0] == String.class;
assert typeArgs[1] == Integer.class;
And from method references:
Comparator<String> comparator = String::compareToIgnoreCase;
Class<?> typeArg = TypeResolver.resolveRawArgument(Comparator.class, comparator.getClass());
assert typeArg == String.class;
We can reify more complex generic type parameters:
interface Foo<T> {}
class Bar implements Foo<List<Integer>> {}
Type typeArgs = TypeResolver.reify(Foo.class, Bar.class);
ParameterizedType paramType = (ParameterizedType) typeArgs;
Type[] actualTypeArgs = paramType.getActualTypeArguments();
ParameterizedType arg = (ParameterizedType)actualTypeArgs[0];
assert paramType.getRawType() == Foo.class;
assert arg1.getRawType() == List.class;
assert arg1.getActualTypeArguments()[0] == Integer.class;
We can also resolve the raw class for type parameters on fields and methods:
class Entity<ID extends Serializable> {
ID id;
void setId(ID id) {}
}
class SomeEntity extends Entity<Long> {}
Type fieldType = Entity.class.getDeclaredField("id").getGenericType();
Type mutatorType = Entity.class.getDeclaredMethod("setId", Serializable.class).getGenericParameterTypes()[0];
assert TypeResolver.resolveRawClass(fieldType, SomeEntity.class) == Long.class;
assert TypeResolver.resolveRawClass(mutatorType, SomeEntity.class) == Long.class;
And we can reify generic type parameters from fields or methods.
Common Use Cases
Layer supertypes often utilize type parameters that are populated by subclasses. A common use case for TypeTools is to resolve the type arguments for a layer supertype given a sub-type.
Following is an example Generic DAO layer supertype implementation:
class Device {}
class Router extends Device {}
class GenericDAO<T, ID extends Serializable> {
protected Class<T> persistentClass;
protected Class<ID> idClass;
private GenericDAO() {
Class<?>[] typeArguments = TypeResolver.resolveRawArguments(GenericDAO.class, getClass());
this.persistentClass = (Class<T>) typeArguments[0];
this.idClass = (Class<ID>) typeArguments[1];
}
}
class DeviceDAO<T extends Device> extends GenericDAO<T, Long> {}
class RouterDAO extends DeviceDAO<Router> {}
We can assert that type arguments are resolved as expected:
RouterDAO routerDAO = new RouterDAO();
assert routerDAO.persistentClass == Router.class;
assert routerDAO.idClass == Long.class;
Additional Features
By default, type variable information for each resolved type is weakly cached by the TypeResolver. Caching can be enabled/disabled via:
TypeResolver.enableCache();
TypeResolver.disableCache();
Additional Notes
On Lambda Support
Lambda type argument resolution is currently supported for:
- Oracle JDK 8, 9
- Open JDK 8, 9
On Unresolvable Lambda Type Arguments
When resolving type arguments with lambda expressions, only type parameters used in the functional interface's method signature can be resolved. Ex:
interface ExtraFunction<T, R, Z> extends Function<T, R>{}
ExtraFunction<String, Integer, Long> strToInt = s -> Integer.valueOf(s);
Class<?>[] typeArgs = TypeResolver.resolveRawArguments(Function.class, strToInt.getClass());
assert typeArgs[0] == String.class;
assert typeArgs[1] == Integer.class;
assert typeArgs[2] == Unknown.class;
Since the type parameter Z in this example is unused by Function, its argument resolves to Unknown.class.
On OSGi Support
When using TypeTools in an OSGi environment where lambda or method reference type argument resolution is desired, the sun.reflect system package should be exported to the application bundles. For example, for Felix, add the following to your config.properties file:
org.osgi.framework.system.packages.extra=sun.reflect
Docs
JavaDocs are available here.
License
Copyright 2010-2019 Jonathan Halterman and friends. Released under the Apache 2.0 license.
265 Jan 2, 2023
2 Mar 5, 2022
5.9k Jan 5, 2023
2.6k Jan 7, 2023
12 Oct 25, 2022
17 Jan 5, 2023
4 Jan 14, 2022
136 Aug 25, 2022
543 Nov 23, 2022
225 Dec 24, 2022
15 Jan 19, 2022
22 Nov 19, 2022
9 Dec 30, 2021
307 Dec 26, 2022
5 Jun 24, 2022
19 Nov 21, 2022
6 Jul 21, 2022
9.2k Jan 1, 2023