Reflection of classes of all active packages is triggered through the bootstrap's
initializeReflectionService() method. In a development context, single classes
may be re-reflected once files are modified whereas in a production context
reflection is done once and successive requests read from the frozen caches for
performance reasons.
The list of available classes is determined by the CompiletimeObjectManager which
also triggers the initial build of reflection data in this service.
The invalidation of reflection cache entries is done by the CacheManager which
in turn is triggered by signals sent by the file monitor.
The internal representation of cache data is optimized for memory consumption and
speed by using constants which have an integer value.