CRM-16373 - Bootstrap subsystems in more predictable order
authorTim Otten <totten@civicrm.org>
Sat, 19 Sep 2015 05:09:01 +0000 (22:09 -0700)
committerTim Otten <totten@civicrm.org>
Mon, 21 Sep 2015 04:24:28 +0000 (21:24 -0700)
commit836178864b970fe12e529f1f3e43047cfa185d68
tree1d6f3c6fc71fb8581fd24466a842c44178b8d02b
parent2b2c4099da39bbb822f29c05c39c44a094fc6554
CRM-16373 - Bootstrap subsystems in more predictable order

Several subsystems were initialized on-demand. This had a weird side-effect
where the container would start initializing and call another service, which
would then (indirectly) try to initialize another container. The two container
instances would not be the same.

This revision enforces a more carefully considered sequence of events (which
will be documented in the wiki page, "Bootstrap Reference").
CRM/Contact/BAO/GroupContactCache.php
CRM/Core/BAO/Cache.php
CRM/Core/Config.php
CRM/Core/Config/Runtime.php
CRM/Mailing/BAO/Mailing.php
CRM/Mailing/BAO/MailingJob.php
Civi.php
Civi/Core/Container.php
api/v3/Job.php
bin/ContributionProcessor.php