Why don't you just use the inclusion and exclusion rules in the aop.xml files to decide which classes actually get loaded into the World map?
Andy Clement wrote: > > Given that doing the right thing with freeing memory is non trivial, I was > thinking just now about an interim measure. A user callable API where you > could indicate to the AspectJ infrastructure that you *knew* the > classloader > had finished loading everything you wanted it to. Upon making the API > call > we would immediately discard the whole weaver *but* keep a note of the > classloader so that any future attempts to load classes that would have > been > woven will receive suitable warning/error messages. I'll take any > comments > anyone has on doing something like that... I'm not sure how easy it is for > you to determine when you know everything has been loaded.. > > Cheers > -- View this message in context: http://old.nabble.com/Memory-consumption-problems-tp18649090p26607167.html Sent from the AspectJ - users mailing list archive at Nabble.com. _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
