Doorgaan naar hoofdcontent

Annotation scanning done easy

We all love annotations. Really, they're nice markers for your pointcuts, create the option to have cross cutting concerns easily (i.e. only log these marked fields, or mask these annotated fields when logging).

However, we do need to be able to *get* to those annotations at runtime to inject those fancy tricks we have up our sleeve.

In comes the beautiful google reflections library which allows us to scan the class files for annotations.
Of course, we made those annotations available at runtime, right?
If not, add @Retention(RetentionPolicy.RUNTIME)to the annotation ;)

So, scanning at runtime done easy:
Collection<URL> urls = ClasspathHelper.forPackage("nl.shopname.location.domain");
 

Reflections reflections =
                new Reflections(new ConfigurationBuilder().setUrls(urls).setScanners(new FieldAnnotationsScanner()));


Set<Field> fieldsWithAnnotation = <reflections.getFieldsAnnotatedWith(MyAnnotation.class);

And we're done. We can scan for fields, types, and then do cool things with them through the reflection if necessary. But that's a straightforward trick, maybe for a late post. Until then, use the library's javadoc.

Mind, in spring we can scan spring annotations with the spring scanner. This is a more generic variant...

Reacties

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...

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.

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.