Doorgaan naar hoofdcontent

Generic reflections in spring

Oh my. Reflection on generics. That's not always nice.
So, here goes.
As can be easily found, it is possible to determine the actual type of a generic class at runtime.
And in the code we get a number of lists<>... and we want to sort them by class hierarchy (so, String extends Object, and thus List<String> should go after List<Object>)
Our compare method then needs to look like this:
compare( List left, List right) {
Type type = left.getClass().getGenericSuperclass()
if(type instanceof ParameterizedType) {// it is a generic
  ParameterizedType pType = (ParameterizedType) type;
  Type[] actualTypes = pType.getActualTypeArguments();
  // and then we have an array, which in this case should be String.class and Object.class, which we can then compare
  }
...
}

This is nice, but spring kinda has the problem that those objects *might* be more then they are... they might be AOP'd!
In that case, we do not get the actual objects, but proxies... which, of course, do *not* have the same inheritance tree. To get the actual classes in that case, use the following:

            private Class<?> getClass(Object clazzInstance) {
                // if it is a (spring) proxy, find the actual type behind it
                Class<?> clazz = clazzInstance.getClass();
                if(Advised.class.isAssignableFrom(clazz)){
                    return (Class<>) ((Advised)clazzInstance).getTargetSource().getTargetClass();
                }
                return clazz;
            } 

Labels

Labels:

Reacties

Een reactie posten

Populaire posts van deze blog

Spring's conditional annotation with properties

Spring has a nice @Conditional annotation, to have the option to have beans be available in the context depending a specific condition (Of course, this can also be realized by using @Configuration objects, but that's a different post). Ideally, we'd have the option to have a condition evaluate to true or false depending on a property. Sadly, Spring does not support that out of the box. Googling and looking around gives a partial solution, but the complete one here, so we won't forget: /** * Components annotated with ConditionalOnProperty will be registered in the spring context depending on the value of a * property defined in the propertiesBeanName properties Bean. */ @Target({ ElementType.TYPE, ElementType.METHOD }) @Retention(RetentionPolicy.RUNTIME) @Conditional(OnPropertyCondition.class) public @interface ConditionalOnProperty { /** * The name of the property. If not found, it will evaluate to false. */ String value(); /** * if the p...
Een reactie posten
Meer lezen

OSGI insights without sonar

So I was on a project without sonar. Oh my. Well, it was an OSGI project, so the problems couldn't be that bad, right? But how good were they (and what things were bad?) I found Stan4j , a code analysis tool for eclipse, which draws nice graphs and can handle osgi pretty well it seems. Now I can see that dependencies/bundle names aren't properly aligned (even though OSGI doesn't complain), etc.
Een reactie posten
Meer lezen

JPA and transactions

So I was working with JPA and transactions. Consider the following: In bean 1, with implicit TX 1, managed entities are loaded/created,and returned in bean 2, with implicit TX 2, entities are modified in bean 3, with NO TX, bean 1 is called, and the results are passed to bean 2. and bean 4 is similar to bean 3, but with it's own transaction, TX3 What happens when bean 3 finishes: are the entities updated? What happens when bean 4 finishes, are the entities updated? The answer to this is simple; entities are managed through a persistance context. That context is tied to the transaction. So in bean 2, there is a difference. When called from bean 3, it runs in a different transaction then bean 1, and thus a different persistance context, and thus the entities are not managed 'by this transaction'.When called from bean 4, it all runs in the same transaction, TX3, and the results are persisted.
Een reactie posten
Meer lezen