Configurable vs Component with Spring and AspectJ

spring annotations aop spring-aop configurable
DragonFax picture DragonFax · May 20, 2009 · Viewed 9.3k times · Source

When using AspectJ, why use @Component over @Configurable.

I've got Spring and AspectJ setup for @Transactional support, aspects on self-invocation, and injection into JPA entities. This works great.

I'm using @Component for most classes that need injection, and thus either having them injected into their dependencies. Or, when I can't, injecting the ApplicationContext and then using getBean() as a last resort. And I'm reserving @Configurable for only JPA entities (Hibernate) that need injection. I've also started using @Configurable for jUnit tests, to make writing tests easy. This also works great.

But I'm curious. If AspectJ is now auto-injecting (beanifying) anything with the @Configurable annotation, regardless of how its constructed; getBean(), new(), @Autowired. Why wouldn't I just switch to using @Configurable for all my beans? Then I can do away with the application context and getBean() altogether, and just new() any classes I can't inject.

I realize that I made no mention of XML bean configuration. I don't shy away from that, but this project doesn't happen to require any. I just constructor or setter inject the dependencies when testing. very easy.

Answer

skaffman picture skaffman · Jun 16, 2009

@Component is a Spring marker interface which can give Spring clues when it comes to auto-detection of beans.

@Configurable is a marker used by the AOP load-time-weaving stuff.

The two don't really have much to do with each other.

Related questions

Spring AOP: @annotation(annotation)

I am (of course) trying to maintain a project using many constructs I don't know that well. In the course of attempting to figure out the AOP use within Spring, I came across methods with the following annotation: @Around(value = "@…

Read More
Telling IntelliJ IDEA which methods not to identify as unused

IntelliJ IDEA has a handy feature to detect unused methods and show them in grey, hinting a potential warning for dead code. Some methods, however, are not executed directly but via reflection. A good example would be @RequestMapping-annotated methods which …

Read More
What's the difference between @Component, @Repository & @Service annotations in Spring?

Can @Component, @Repository and @Service annotations be used interchangeably in Spring or do they provide any particular functionality besides acting as a notation device? In other words, if I have a Service class and I change the annotation from @Service …

Read More