Springize Aggregation

Refactoring of the aggregator to springify (is that a word?) most classes in Aggregation package into components.. At the very least, the refactoring is going to enable us to better handle caching and rendering AOP actions. This work will provide for AOP interception into the aggregation engine for statistical and performance analytics, and other interception use cases. My aim is to fully springize the aggregation engine.

Goals of refactoring:

• enable my development (already started) of a second multithreaded/async aggregator solution
• make the work manager replaceable in Spring
• enable point cuts for AOP required features for final release:

• caching handled by interception during aggregation (dont start thread for cached content)
• statistical interception points for portlet usage stats