Automatic flushing of AOP Proxy Cache
Similar to the automatic flushing of the Reflection Cache (or parts of it) the AOP proxy classes should be rebuilt whenever a class is modified - at least in the development context. However, that's only realistic if rebuilding the cache doesn't take too long so it remains to be seen if this is realistic or not.
- FLOW3: (AOP) Implemented a completely new initialization method for the AOP framework which now supports some intelligent caching mechanism: If class code changes somewhere, the affected proxy classes are rebuilt automatically, still valid proxy classes are untouched. If aspects change (or are added / removed) all proxy classes are rebuilt. All based on the new File Monitor feature. Resolves #2305
- FLOW3: Fixed configuration to assure that the file monitoring is really disabled in Production context.