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

Being a Vegetarian

I am a Proud Vegetarian. I don't eat Meat or Eggs. People say its hard here in US to be one. I beg to differ. The mere fact that I am hail and healthy these 4 years is a definitive proof. Apart from being bullied and trash talked by The Meat-Eaters, There is really nothing that makes this choice of mine any more than a debatable issue at a lunch or dinner. Other things aside, I am writing this blog having watched a PETA Video. Before you click on the play button, I ask you - If you are a vegetarian : Dont watch it. If you are not : Dare to watch it till the end. If you think going veg is just a fashion, think again . Even if you just want to do it for Fashion . Do it. Go Vegetarian. And Feel better asking the waiter for a Vegetarian Entrée in your next lunch.

Using Equinox CommandProvider to make OSGi console interactive.

After fiddling with the First Bundles that "Hello World"-ed upon Activation, You want to see more interactivity in OSGi. Although Using OSGi for an interactive Command Line Application would be like this one would be, well, a callable over-kill, I am going to start with an example and Expand it in later posts. So, please Welcome CommandProvider. CommandProvider is an EQUINOX specific API for extending the Console. This basic Example illustrates how to get a command from console and do something in java and also gets your feet wet on Service Registry package com.so.examples.commandconsole; import org. eclipse .osgi.framework.console .CommandInterpreter; import org.eclipse.osgi.framework.console.CommandProvider; public class DisplayMessageCommand implements CommandProvider { public void _say(CommandInterpreter ci) { ci.print("You said:" + ci.nextArgument()); } @Override public String getHelp() { return "\tsay - repeats what you say\n"; } }

How to Make a Local (Offline) Repository in Ubuntu / Debian

If you are in a place where you dont have internet (or have a bad one) You want to download .deb packages and install them offline. Each deb file is packaged as a seperate unit but may contain dependencies (recursively). apt-get automagically solves all the dependencies and installs all that are necessary. Manually install deb files one by one resolving each dependency would be tedious. A better approach is to make your own local repository. Before you actually make a repo, You need *all* deb files. You dont practically have to mirror all of the packages from the internet, but enough to resolve all dependencies. Also, You have to make sure, you are getting debs of the correct architecture of your system (i386 etc) # 1. make a dir accessible (atleast by root) sudo mkdir /var/my-local-repo # 2. copy all the deb files to this directory. # 3. make the directory as a sudo dpkg-scanpackages /var/my-local-repo /dev/null > \ /var/my-local-repo/Packages # 4. add the local repo to sour