[aspectj-dev] Caching weaved classes

[Simone Gianni <simoneg@xxxxxxxxxx>]

Hi all,
in the Apache Magma Lab, we're using LTW for our users development 
environment. Lately I rewrote this part to proper pipeline class 
loading, AspectJ weaving and OpenJPA enhancing. While rewriting it, I 
kept on thinking on LTW classes caching performed by Equinox Aspects to 
reduce load time, which in fact is a bit long being more than 30 seconds 
for each cycle even for a basic project. Actually, OSGI has the 
advantage of knowing which bundle weaves which other bundles, and simply 
trigger a reload of those bundles if an aspect has changed. But since 
recently version 1.6.3 focused on separating matching from weaving, and 
since the matching part is obviously the first part that the 
WeavingAdaptor computes upon startup, the idea kept on coming up.

Do you have any pointers for me to start? Do you think it's possible? Do 
you think it's useful?

Simone

--
Simone Gianni            CEO Semeru s.r.l.           Apache Committer
http://www.simonegianni.it/