Bug #3240

AOP cache is not emptied if class file is deleted

Added by Robert Lemke about 6 years ago. Updated almost 5 years ago.

Status:Resolved Start date:2009-05-07
Priority:Must have Due date:
Assigned To:Robert Lemke % Done:

100%
Category:Monitor
Target version:TYPO3 Flow Base Distribution - 1.0 alpha 2
PHP Version: Complexity:
Has patch: Affected Flow version:

Description

I'm not 100% sure but this needs to be checked: If a class file is deleted or moved to a different namespace, the AOP Framework still tries to execute the cached proxy code. Maybe that's a bug in the File Monitor?

Related issues

related to TYPO3.Flow - Feature #3649: Caches should be flushed on package version number changes Resolved 2009-06-12
related to TYPO3.Flow - Bug #2974: Aspect / Proxy Cache is not emptied automatically if an i... New 2009-03-25

Associated revisions

Revision 44ad6e9b
Added by Robert Lemke about 6 years ago

  • [+FEAT] FLOW3 (Utility): The Files::readDirectoryRecursively() function now supports an optional $suffix parameter which allows for filtering the list of files by a given extension.
  • [+FEAT] FLOW3 (Monitor): The File Monitor now supports monitoring of directories. Once a directory is monitored, any change of files or directories within the directory (recursively) will emit a respective signal. Resolves #3736
  • [FIX] FLOW3 (Monitor): Deleted and newly created files are now properly detected by the File Monitor after monitoring of whole directories has been introduced. Resolves #3240
  • [+FEAT] FLOW3 (Core): FLOW3 will now check and cache its own revision. If the revision changes (due to an upgrade or update from Subversion), all registered caches are flushed automatically. This prevents PHP errors due to non backwards compatible cache structures in newer versions of FLOW3. Resolves #3649

History

#1 Updated by Robert Lemke about 6 years ago

  • Target version set to 283

#2 Updated by Robert Lemke about 6 years ago

  • Priority changed from Should have to Must have
  • Target version changed from 283 to 1.0 alpha 2

#3 Updated by Karsten Dambekalns about 6 years ago

  • Status changed from New to Accepted
  • Assigned To set to Robert Lemke

#4 Updated by Robert Lemke about 6 years ago

The problem lies in the Monitoring mechanism, not in the AOP framework.

#5 Updated by Robert Lemke about 6 years ago

  • Status changed from Accepted to Resolved
  • % Done changed from 0 to 100

Applied in changeset r2645.

Also available in: Atom PDF