A small but useful addition to the common-spring-aspects project: forked execution of a bean method.
Using the ForkAspect, it is possible to define bean methods to be executed in a separate thread. This is useful to avoid waiting on slow methods whose results we do not actually need to proceed (common examples - email sending, statistics event registration, etc).
It is amazing how many people still write some log.debug() to track execution time of their methods or create a caching proxy class for each class they want to cache.
Come on, this is done million times before, why not reuse ?
Today I've written some documentation on the Common Spring aspects project. This project collects some handy aspects that I find myself using on almost every project - currently, performance logging (using JaMon library) and caching bean method invocations results (using Ehcache). The code itself is fairly small, mostly it just delegates execution to the respective library.
Posts
All Comments
