In short, I have a similar need to what Andrew Scott asks for here:
https://groups.google.com/forum/#!msg/coldbox/PTpwoGZzJzg/dyUSyTaTIocJ
I have an application which isn’t behaving, and it appears to be related to certain code being run before Wirebox is ready, and thus being unable to find dependencies.
Initially I thought the issue was with interceptors, and I’ve tried resolving it by moving from structs in configure() to manual registerInterceptor calls in afterConfigurationLoad (both in core application and in various modules), which appeared to work, except I then have issues with modules (in particular a customised version of ContentBox).
If I change the afterConfigurationLoad to preModuleLoad (after seeing Brad’s list - I would never have guessed that came first from the http://wiki.coldbox.org/wiki/Interceptors.cfm docs), I then get dependency errors again.
So yeah, what I really need is a precise diagram/explanation of the lifecycle. The one Curt linked to (http://wiki.coldbox.org/wiki/RequestLifecycles.cfm) would be fine, except it misses too much information: it doesn’t include preModuleLoad; I don’t understand why Configuration File Loaded is separated from afterConfigurationLoad by two steps; is “Modules Activated” the same as Modules being Loaded; at what point does Wirebox get involved - it is only mentioned in the non-fwreinit path; etc…