Skip to main content

Getting a Java Type Parameter class at runtime

Certain use cases like deserializing a collection requires knowing the type of the declared field. As the common understanding goes, Type Parameters are erased at build time. So How do we get them?

Its a common misconception that "Type Parameters are erased at build time" - Instead what is actually happening is - Generic collections are converted to raw types. The class definition is NOT modified at build/run time. The Type Parameter(s) can be accessed from the class definition through reflection.

For example:

Lets say here is a Bean

public class Document {
 private List<Model> models;
        ..
}

Given doc, an instance of Document, at runtime, getting the type of doc.models by traditional reflection, can only get that its type is java.util.List

//somewhere in runtime
Document doc = new Document();

 Field f = bean.getClass().getDeclaredField(field);
 f.setAccessible(true);
 assert f.getClass() == List.class

To get the type from parameter, Assuming we know that it is a ParameterizedType (like List<T>)

private <T> Class getListType(T bean, String field) throws NoSuchFieldException {
 Class childType;
 Field f = bean.getClass().getDeclaredField(field);
 f.setAccessible(true);
 childType = (Class) ((ParameterizedType) f.getGenericType()).getActualTypeArguments()[0];
 return childType;
}

//somewhere in runtime
Document doc = new Document();
assert getListType(doc, "models") == Model.class


The same logic can be applied to get multi parameter types (like Map)

 keyType = (Class) ((ParameterizedType) f.getGenericType()).getActualTypeArguments()[0];
 valueType = (Class) ((ParameterizedType) f.getGenericType()).getActualTypeArguments()[1];

Popular posts from this blog

Powered By

As it goes, We ought to give thanks to people who power us. This page will be updated, like the version page , to show all the tools, and people this site is Powered By! Ubuntu GIMP Firebug Blogger Google [AppEngine, Ajax and other Apis] AddtoAny Project Fondue jQuery

Decorator for Memcache Get/Set in python

I have suggested some time back that you could modularize and stitch together fragments of js and css to spit out in one HTTP connection. That makes the page load faster. I also indicated that there ways to tune them by adding cache-control headers. On the server-side however, you could have a memcache layer on the stitching operation. This saves a lot of Resources (CPU) on your server. I will demonstrate this using a python script I use currently on my site to generate the combined js and css fragments. So My stitching method is like this @memize(region="jscss") def joinAndPut(files, ext): res = files.split("/") o = StringIO.StringIO() for f in res: writeFileTo(o, ext + "/" + f + "." + ext) #writes file out ret = o.getvalue() o.close() return ret; The method joinAndPut is * decorated * by memize. What this means is, all calls to joinAndPut are now wrapped (at runtime) with the logic in memize. All you wa...

Faster webpages with fewer CSS and JS

Its easy, have lesser images, css and js files. I will cover reducing number of images in another post. But If you are like me, You always write js and css in a modular fashion. Grouping functions and classes into smaller files (and Following the DRY rule, Strictly!). But what happens is, when you start writing a page to have these css and js files, you are putting them in muliple link rel=style-sheet or script tags. Your server is being hit by (same) number of HTTP Requests for each page call. At this point, its not the size of files but the number server roundtrips on a page that slows your page down. Yslow shows how many server roundtrips happen for css and js. If you have more than one css call and one js call, You are not using your server well. How do you achieve this? By concatinating them and spitting out the content as one stream. So Lets say I have util.js, blog.js and so.js. If I have a blog template that depends on these three, I would call them in three script tags. Wh...